These are opportunities to speed up your application by optimizing the following resources.
Enable text compression: 2,25 s
Defer offscreen images: 1,8 s
Keep server response times low (TTFB): 0,02 s
Diagnostics
More information about the performance of your application.
Text is invisible while webfonts are loading
Uses inefficient cache policy on static assets: 7 assets found
Has significant main thread work: 3.460 ms
Critical Request Chains: 2 chains found
Progressive Web App
These checks validate the aspects of a Progressive Web App, as specified by the baseline PWA Checklist.
Does not respond with a 200 when offline
User will not be prompted to Install the Web App: Failures: No manifest was fetched, Site does not register a service worker.
Does not register a service worker
Does not provide fallback content when JavaScript is not available: The page body should render some content if its scripts are not available.
Is not configured for a custom splash screen: Failures: No manifest was fetched.
Address bar does not match brand colors: Failures: No manifest was fetched.
Additional items to manually check
These checks are required by the baseline PWA Checklist but are not automatically checked by Lighthouse. They do not affect your score but it's important that you verify them manually.
[ ] 1. Site works cross-browser
[x] 2. Page transitions don't feel like they block on the network
[x] 3. Each page has a URL
Accessibility
These checks highlight opportunities to improve the accessibility of your web app. Only a subset of accessibility issues can be automatically detected so manual testing is also encouraged.
Color Contrast Is Satisfactory
These are opportunities to improve the legibility of your content.
Background and foreground colors do not have a sufficient contrast ratio.
Additional items to manually check
[ ] 1. These items address areas which an automated testing tool cannot cover. Learn more in our guide on conducting an accessibility review.
[ ] 2. The page has a logical tab order
[ ] 3. Interactive controls are keyboard focusable
[ ] 4. The user's focus is directed to new content added to the page
[ ] 5. User focus is not accidentally trapped in a region
[ ] 6. Custom controls have associated labels
[ ] 7. Custom controls have ARIA roles
[ ] 8. Visual order on the page follows DOM order
[ ] 9. Offscreen content is hidden from assistive technology
[ ] 10. Headings don't skip levels
[ ] 11. HTML5 landmark elements are used to improve navigation
Best Practices
Does not use HTTP/2 for all of its resources: 7 requests not served via HTTP/2
Includes front-end JavaScript libraries with known security vulnerabilities: 1 vulnerability detected
Browser errors were logged to the console
SEO
These checks ensure that your page is optimized for search engine results ranking. There are additional factors Lighthouse does not check that may affect your search ranking.
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages.
Document doesn't use legible font sizes: 86.05% of text is too small. 14% legible text
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Document does not have a meta description
Additional items to manually check
[ ] 1. Run these additional validators on your site to check additional SEO best practices.
Network throttling: 150 ms TCP RTT, 1.638,4 Kbps throughput (Simulated)
CPU throttling: 4x slowdown (Simulated)
User agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36
Generated by Lighthouse 3.0.1
Pingdom
F 1 point | Leverage browser caching
The following cacheable resources have a short freshness lifetime. Specify an expiration at least one week in the future for the following resources:
C 75 points | Specify a Vary: Accept-Encoding header
The following publicly cacheable, compressible resources should have a "Vary: Accept-Encoding" header:
B 87 points | Specify a cache validator
The following resources are missing a cache validator. Resources that do not specify a cache validator cannot be refreshed efficiently. Specify a Last-Modified or ETag header to enable cache validation for the following resources:
This website does not appear to be associated with a Facebook page. This website did not contain a link to Facebook.
Twitter page
This website does not appear to be associated with a Twitter account. This website did not contain a link to Twitter.
Printability
0% of pages are optimized for printing: this website does not appear to be optimised for printing (using CSS).
Headings
No pages were found to be using defined headings. This means that users and search engines may find it harder to determine the content of this website's page. Correctly defined headings aid accessibility and are particularly important for search engine optimization.
Title tag check
[X] Length: 8 signs (Recomended: 35-65 signs)
Description check
[X] Description tag not found
Favicon
[X] IE 8 | Icon "type" is not correct
[X] IE 9-10 | Icon not set
[X] Android | Icon not set
[X] iOS | Icon not set
[X] OSX | Icon not set
[X] Windows 8 | Tag "TileColor" not setTag "TileImage" not set
[X] Windows 8.1 | Tags is present
[X] Desktop | Icon not set
Canonical link check
[X] Canonical Link tag not found
www to non www redirect
[X] www / non-www page redirects are not configured
Robots.txt
[X] Robots.txt is not available
Sitemap
[ ] Use a sitemap to submit all pages of your website to search engines.
Speed
Eliminate render-blocking JavaScript and CSS in above-the-fold content
3 images are resized on browser side
Images must not be delivered larger than they are actually displayed to avoid loading unnecessary data.
1 critical dependency detected
The failure of a third-party content provider could bring an overall breakdown of your website.
This resource represents a SPOF for this page:
It is critical to restrict the origin of the contents of your webpage to protect your website from cross-site scripting attacks (XSS).
Here's an example:
Protect yourself from malicious exploitation via MIME sniffing.
Your site doesn't use Open Graph properties
You can help social networks understand information related to the page by using Open Graph properties.
Several properties allow social networks to learn more about the page's content. This is recommend using at least the required properties:
Thanks very much for putting this report together! I have fixed my server's text compression, so that helped performance a decent amount. Next, I need to work on optimizing images.
Lighthouse Report
Performance
Metrics
Opportunities
These are opportunities to speed up your application by optimizing the following resources.
Diagnostics
Progressive Web App
These checks validate the aspects of a Progressive Web App, as specified by the baseline PWA Checklist.
Additional items to manually check These checks are required by the baseline PWA Checklist but are not automatically checked by Lighthouse. They do not affect your score but it's important that you verify them manually.
Accessibility
These checks highlight opportunities to improve the accessibility of your web app. Only a subset of accessibility issues can be automatically detected so manual testing is also encouraged. Color Contrast Is Satisfactory These are opportunities to improve the legibility of your content.
Additional items to manually check
Best Practices
SEO
These checks ensure that your page is optimized for search engine results ranking. There are additional factors Lighthouse does not check that may affect your search ranking.
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages.
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Additional items to manually check
Runtime settings
Pingdom
F 1 point | Leverage browser caching The following cacheable resources have a short freshness lifetime. Specify an expiration at least one week in the future for the following resources:
C 75 points | Specify a Vary: Accept-Encoding header The following publicly cacheable, compressible resources should have a "Vary: Accept-Encoding" header:
B 87 points | Specify a cache validator The following resources are missing a cache validator. Resources that do not specify a cache validator cannot be refreshed efficiently. Specify a Last-Modified or ETag header to enable cache validation for the following resources:
Others
Facebook page
This website does not appear to be associated with a Facebook page. This website did not contain a link to Facebook.
Twitter page
This website does not appear to be associated with a Twitter account. This website did not contain a link to Twitter.
Printability
0% of pages are optimized for printing: this website does not appear to be optimised for printing (using CSS).
Headings
No pages were found to be using defined headings. This means that users and search engines may find it harder to determine the content of this website's page. Correctly defined headings aid accessibility and are particularly important for search engine optimization.
Title tag check
Description check
Favicon
Canonical link check
www to non www redirect
Robots.txt
Sitemap
Speed
Eliminate render-blocking JavaScript and CSS in above-the-fold content
3 images are resized on browser side
Images must not be delivered larger than they are actually displayed to avoid loading unnecessary data.
1 critical dependency detected
The failure of a third-party content provider could bring an overall breakdown of your website. This resource represents a SPOF for this page:
The Content Security Policy is missing
It is critical to restrict the origin of the contents of your webpage to protect your website from cross-site scripting attacks (XSS). Here's an example:
Disable the auto detection of resource type
Protect yourself from malicious exploitation via MIME sniffing.
Your site doesn't use Open Graph properties
You can help social networks understand information related to the page by using Open Graph properties. Several properties allow social networks to learn more about the page's content. This is recommend using at least the required properties:
<meta property="og:title" content="The title" />
<meta property="og:type" content="The type" />
<meta property="og:url" content="http://url.com/" />
<meta property="og:image" content="http://image.jpg" />