Bye.fyi Site Title
bye.fyi | Keyword Rankings
Bye.fyi Meta Description
Open Source Keyword Rankings
Bye.fyi Test Results
Bye.fyi Mobile Performance: 80/100
Quick overview:
Opportunities
These suggestions can help your page load faster. They don't directly affect the Performance score.
Properly size images. Potential savings of 193 KB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.
Remove unused JavaScript. Potential savings of 169 KB
Remove unused JavaScript to reduce bytes consumed by network activity. Learn more.
Remove unused CSS. Potential savings of 191 KB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.
Enable text compression. Potential savings of 115 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.
Eliminate render-blocking resources. Potential savings of 150 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Does not use passive listeners to improve scrolling performance
Consider marking your touch and wheel event listeners as `passive` to improve your page's scroll performance. Learn more.
Avoid `document.write()`
For users on slow connections, external scripts dynamically injected via `document.write()` can delay page load by tens of seconds. Learn more.
Reduce the impact of third-party code
Third-party code blocked the main thread for 590 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more.
Serve static assets with an efficient cache policy
9 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.
Minimize main-thread work
2.9 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more
Reduce JavaScript execution time
1.5 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.
Avoid large layout shifts
3 elements found
These DOM elements contribute most to the CLS of the page.
Keep request counts low and transfer sizes small
46 requests • 908 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.
Avoid chaining critical requests
7 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.
Largest Contentful Paint element
1 element found
This is the element that was identified as the Largest Contentful Paint. Learn More
Bye.fyi Mobile SEO: 100/100
Quick overview:
Bye.fyi Mobile Best Practices: 85/100
Quick overview:
Trust and Safety
Links to cross-origin destinations are unsafe
Add `rel="noopener"` or `rel="noreferrer"` to any external links to improve performance and prevent security vulnerabilities. Learn more.
Does not use HTTPS
1 insecure request found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being servedover HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more.
Bye.fyi Mobile Progressive Web App: 46/100
Quick overview:
Fast and reliable
`start_url` does not respond with a 200 when offline
A service worker enables your web app to be reliable in unpredictable network conditions. Learn more. No usable web app manifest found on page.
Current page does not respond with a 200 when offline
If you're building a Progressive Web App, consider using a service worker so that your app can work offline. Learn more.
PWA Optimized
Does not provide a valid `apple-touch-icon`
For ideal appearance on iOS when users add a progressive web app to the home screen, define an `apple-touch-icon`. It must point to a non-transparent 192px (or 180px) square PNG. Learn More.
Is not configured for a custom splash screen
A themed splash screen ensures a high-quality experience when users launch your app from their homescreens. Learn more. Failures: No manifest was fetched.
Manifest doesn't have a maskable icon
A maskable icon ensures that the image fills the entire shape without being letterboxed when installing the app on a device. Learn more. No manifest was fetched
Does not set a theme color for the address bar.
The browser address bar can be themed to match your site. Learn more. Failures: No manifest was fetched,
No `<meta name="theme-color">` tag found.
Installable
Web app manifest does not meet the installability requirements
Browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement. Learn more. Failures: No manifest was fetched.
Does not register a service worker that controls page and `start_url`
The service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. Learn more.
Does not use HTTPS
1 insecure request found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being servedover HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more.
Bye.fyi Mobile Accessibility: 96/100
Quick overview:
Contrast
These are opportunities to improve the legibility of your content.
Background and foreground colors do not have a sufficient contrast ratio.
Low-contrast text is difficult or impossible for many users to read. Learn more.
Similar sites
Similar tests
www.bye.com
www.bye.net
www.bye.org
www.bye.info
www.bye.biz
www.bye.us
www.bye.mobi
www.ye.fyi
www.bye.fyi
www.vye.fyi
www.bvye.fyi
www.vbye.fyi
www.gye.fyi
www.bgye.fyi
www.gbye.fyi
www.hye.fyi
www.bhye.fyi
www.hbye.fyi
www.nye.fyi
www.bnye.fyi
www.nbye.fyi
www.be.fyi
www.bte.fyi
www.byte.fyi
www.btye.fyi
www.bge.fyi
www.byge.fyi
www.bhe.fyi
www.byhe.fyi
www.bue.fyi
www.byue.fyi
www.buye.fyi
www.by.fyi
www.byw.fyi
www.byew.fyi
www.bywe.fyi
www.bys.fyi
www.byes.fyi
www.byse.fyi
www.byd.fyi
www.byed.fyi
www.byde.fyi
www.byr.fyi
www.byer.fyi
www.byre.fyi
www.bye.net
www.bye.org
www.bye.info
www.bye.biz
www.bye.us
www.bye.mobi
www.ye.fyi
www.bye.fyi
www.vye.fyi
www.bvye.fyi
www.vbye.fyi
www.gye.fyi
www.bgye.fyi
www.gbye.fyi
www.hye.fyi
www.bhye.fyi
www.hbye.fyi
www.nye.fyi
www.bnye.fyi
www.nbye.fyi
www.be.fyi
www.bte.fyi
www.byte.fyi
www.btye.fyi
www.bge.fyi
www.byge.fyi
www.bhe.fyi
www.byhe.fyi
www.bue.fyi
www.byue.fyi
www.buye.fyi
www.by.fyi
www.byw.fyi
www.byew.fyi
www.bywe.fyi
www.bys.fyi
www.byes.fyi
www.byse.fyi
www.byd.fyi
www.byed.fyi
www.byde.fyi
www.byr.fyi
www.byer.fyi
www.byre.fyi