Tcrf.net Site Title

The Cutting Room Floor

Tcrf.net Test Results

Tcrf.net Mobile Performance: 91/100
Quick overview:
Opportunities
These suggestions can help your page load faster. They don't directly affect the Performance score.
Enable text compression. Potential savings of 315 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.
Avoid multiple page redirects. Potential savings of 1,110 ms
Redirects introduce additional delays before the page can be loaded. Learn more.
Remove unused JavaScript. Potential savings of 180 KiB
Remove unused JavaScript to reduce bytes consumed by network activity. Learn more.
Eliminate render-blocking resources. Potential savings of 430 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.
Use HTTP/2. 13 requests not served via HTTP/2
HTTP/2 offers many benefits over HTTP/1.1, including binary headers and multiplexing. Learn more.
Serve images in next-gen formats. Potential savings of 27 KiB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.
Remove unused CSS. Potential savings of 28 KiB
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.
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Serve static assets with an efficient cache policy
6 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.
Avoid long main-thread tasks
4 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn more
User Timing marks and measures
1 user timing
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport. Learn More
Keep request counts low and transfer sizes small
16 requests • 502 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.
Avoid chaining critical requests
2 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.

Tcrf.net Mobile SEO: 62/100
Quick overview:
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Links are not crawlable
Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn More
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. Learn more.
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
Add a `<meta name="viewport">` tag to optimize your app for mobile screens. Learn more. No `<meta name="viewport">` tag found
Tap targets are not sized appropriately
Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements. Learn more. Tap targets are too small because there's no viewport meta tag optimized for mobile screens
Document doesn't use legible font sizes
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px. Learn more. Text is illegible because there's no viewport meta tag optimized for mobile screens.
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
Meta descriptions may be included in search results to concisely summarize page content. Learn more.

Tcrf.net Mobile Best Practices: 87/100
Quick overview:
Trust and Safety
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 served over 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.
Includes front-end JavaScript libraries with known security vulnerabilities
3 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers. Learn more.
Tcrf.net Mobile Progressive Web App: 17/100
Quick overview:
PWA Optimized
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.
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 have a `<meta name="viewport">` tag with `width` or `initial-scale`
Add a `<meta name="viewport">` tag to optimize your app for mobile screens. Learn more. No `<meta name="viewport">` tag found
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.
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.
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.
Content is not sized correctly for the viewport
If the width of your app's content doesn't match the width of the viewport, your app might not be optimized for mobile screens. Learn more. The viewport size of 980px does not match the window size of 360px.
Installable
Web app manifest or service worker do not meet the installability requirements
1 reason
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. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement. Learn more.
Tcrf.net Mobile Accessibility: 100/100
Quick overview:
Similar sites
Similar tests
www.tcrf.com
www.tcrf.net
www.tcrf.org
www.tcrf.info
www.tcrf.biz
www.tcrf.us
www.tcrf.mobi
www.crf.net
www.tcrf.net
www.rcrf.net
www.trcrf.net
www.rtcrf.net
www.fcrf.net
www.tfcrf.net
www.ftcrf.net
www.gcrf.net
www.tgcrf.net
www.gtcrf.net
www.ycrf.net
www.tycrf.net
www.ytcrf.net
www.trf.net
www.txrf.net
www.tcxrf.net
www.txcrf.net
www.tdrf.net
www.tcdrf.net
www.tdcrf.net
www.tfrf.net
www.tcfrf.net
www.tvrf.net
www.tcvrf.net
www.tvcrf.net
www.tcf.net
www.tcef.net
www.tcref.net
www.tcerf.net
www.tcdf.net
www.tcrdf.net
www.tcff.net
www.tcrff.net
www.tctf.net
www.tcrtf.net
www.tctrf.net
www.tcr.net
www.tcrc.net
www.tcrfc.net
www.tcrcf.net
www.tcrd.net
www.tcrfd.net
www.tcrr.net
www.tcrfr.net
www.tcrrf.net
www.tcrt.net
www.tcrft.net
www.tcrg.net
www.tcrfg.net
www.tcrgf.net
www.tcrv.net
www.tcrfv.net
www.tcrvf.net
Last Tested: