Save.tf Test Results
Save.tf Mobile Performance: 81/100
Quick overview:
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Avoid large layout shifts
1 layout shift found
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS
Properly size images
Potential savings of 106 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
Reduce unused JavaScript
Potential savings of 25 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
Avoid multiple page redirects
Potential savings of 630 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Largest Contentful Paint element
3,780 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Serve static assets with an efficient cache policy
23 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Ensure text remains visible during webfont load
Leverage the `font-display` CSS feature to ensure text is user-visible while webfonts are loading. Learn more about `font-display`.
Image elements do not have explicit `width` and `height`
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
Preload Largest Contentful Paint image
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more about preloading LCP elements.
Max Potential First Input Delay
180 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.
Save.tf Mobile SEO: 82/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 how to make links crawlable
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 about the meta description.
Save.tf Mobile Best Practices: 83/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 about HTTPS.
Save.tf Mobile Accessibility: 86/100
Quick overview:
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Buttons do not have an accessible name
When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.
Navigation
These are opportunities to improve keyboard navigation in your application.
Heading elements are not in a sequentially-descending order
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.
Similar sites
Similar tests
www.save.com
www.save.net
www.save.org
www.save.info
www.save.biz
www.save.us
www.save.mobi
www.ave.tf
www.save.tf
www.wave.tf
www.swave.tf
www.wsave.tf
www.eave.tf
www.seave.tf
www.esave.tf
www.dave.tf
www.sdave.tf
www.dsave.tf
www.zave.tf
www.szave.tf
www.zsave.tf
www.xave.tf
www.sxave.tf
www.xsave.tf
www.aave.tf
www.saave.tf
www.asave.tf
www.sve.tf
www.sqve.tf
www.saqve.tf
www.sqave.tf
www.swve.tf
www.sawve.tf
www.ssve.tf
www.sasve.tf
www.ssave.tf
www.szve.tf
www.sazve.tf
www.sae.tf
www.sace.tf
www.savce.tf
www.sacve.tf
www.safe.tf
www.savfe.tf
www.safve.tf
www.sage.tf
www.savge.tf
www.sagve.tf
www.sabe.tf
www.savbe.tf
www.sabve.tf
www.sav.tf
www.savw.tf
www.savew.tf
www.savwe.tf
www.savs.tf
www.saves.tf
www.savse.tf
www.savd.tf
www.saved.tf
www.savde.tf
www.savr.tf
www.saver.tf
www.savre.tf
www.save.net
www.save.org
www.save.info
www.save.biz
www.save.us
www.save.mobi
www.ave.tf
www.save.tf
www.wave.tf
www.swave.tf
www.wsave.tf
www.eave.tf
www.seave.tf
www.esave.tf
www.dave.tf
www.sdave.tf
www.dsave.tf
www.zave.tf
www.szave.tf
www.zsave.tf
www.xave.tf
www.sxave.tf
www.xsave.tf
www.aave.tf
www.saave.tf
www.asave.tf
www.sve.tf
www.sqve.tf
www.saqve.tf
www.sqave.tf
www.swve.tf
www.sawve.tf
www.ssve.tf
www.sasve.tf
www.ssave.tf
www.szve.tf
www.sazve.tf
www.sae.tf
www.sace.tf
www.savce.tf
www.sacve.tf
www.safe.tf
www.savfe.tf
www.safve.tf
www.sage.tf
www.savge.tf
www.sagve.tf
www.sabe.tf
www.savbe.tf
www.sabve.tf
www.sav.tf
www.savw.tf
www.savew.tf
www.savwe.tf
www.savs.tf
www.saves.tf
www.savse.tf
www.savd.tf
www.saved.tf
www.savde.tf
www.savr.tf
www.saver.tf
www.savre.tf