Avs.org Site Title
AVS - Home
Avs.org Test Results
Avs.org Mobile Performance: 12/100
Quick overview:
Opportunities
These suggestions can help your page load faster. They don't directly affect the Performance score.
Serve images in next-gen formats. Potential savings of 1,902 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.
Efficiently encode images. Potential savings of 1,235 KiB
Optimized images load faster and consume less cellular data. Learn more.
Avoid multiple page redirects. Potential savings of 1,740 ms
Redirects introduce additional delays before the page can be loaded. Learn more.
Eliminate render-blocking resources. Potential savings of 1,170 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.
Remove unused CSS. Potential savings of 70 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.
Reduce initial server response time. Root document took 1,340 ms
Keep the server response time for the main document short because all other requests depend on it. Learn more.
Minify CSS. Potential savings of 11 KiB
Minifying CSS files can reduce network payload sizes. Learn more.
Remove unused JavaScript. Potential savings of 455 KiB
Remove unused JavaScript to reduce 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.
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.
Serve static assets with an efficient cache policy
84 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.
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.
Reduce the impact of third-party code
Third-party code blocked the main thread for 2,180 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.
Minimize main-thread work
9.0 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more
Avoid enormous network payloads
Total size was 6,252 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.
Reduce JavaScript execution time
5.0 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.
Avoid chaining critical requests
16 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.
Avoid large layout shifts
5 elements found
These DOM elements contribute most to the CLS of the page.
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
176 requests • 6,252 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.
User Timing marks and measures
5 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.
Avoid long main-thread tasks
16 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn more
Avs.org Mobile SEO: 46/100
Quick overview:
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. Description text is empty.
Image elements do not have `[alt]` attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. 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.
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.
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
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
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
robots.txt is not valid
Request for robots.txt returned HTTP status: 500
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more.
Avs.org Mobile Best Practices: 62/100
Quick overview:
User Experience
Serves images with low resolution
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn more.
General
Browser errors were logged to the console
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more
Trust and Safety
Includes front-end JavaScript libraries with known security vulnerabilities
4 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers. Learn more.
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
2 insecure requests 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.
Avs.org Mobile Progressive Web App: 11/100
Quick overview:
PWA Optimized
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 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 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.
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.
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
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
2 insecure requests 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.
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.
Page load is not fast enough on mobile networks
Interactive at 16.4 s
A fast page load over a cellular network ensures a good mobile user experience. Learn more. Your page loads too slowly and is not interactive within 10 seconds. Look at the opportunities and diagnostics in the "Performance" section to learn how to improve.
Avs.org Mobile Accessibility: 76/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.
Form elements do not have associated labels
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more.
Image elements do not have `[alt]` attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more.
`<input type="image">` elements do not have `[alt]` text
When an image is being used as an `<input>` button, providing alternative text can help screen reader users understand the purpose of the button. Learn more.
`<frame>` or `<iframe>` elements do not have a title
Screen reader users rely on frame titles to describe the contents of frames. Learn more.
Links do not have a discernible name
Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn more.
Similar sites
Similar tests
www.avs.com
www.avs.net
www.avs.org
www.avs.info
www.avs.biz
www.avs.us
www.avs.mobi
www.vs.org
www.avs.org
www.qvs.org
www.aqvs.org
www.qavs.org
www.wvs.org
www.awvs.org
www.wavs.org
www.svs.org
www.asvs.org
www.savs.org
www.zvs.org
www.azvs.org
www.zavs.org
www.as.org
www.acs.org
www.avcs.org
www.acvs.org
www.afs.org
www.avfs.org
www.afvs.org
www.ags.org
www.avgs.org
www.agvs.org
www.abs.org
www.avbs.org
www.abvs.org
www.av.org
www.avw.org
www.avsw.org
www.avws.org
www.ave.org
www.avse.org
www.aves.org
www.avd.org
www.avsd.org
www.avds.org
www.avz.org
www.avsz.org
www.avzs.org
www.avx.org
www.avsx.org
www.avxs.org
www.ava.org
www.avsa.org
www.avas.org
www.avs.net
www.avs.org
www.avs.info
www.avs.biz
www.avs.us
www.avs.mobi
www.vs.org
www.avs.org
www.qvs.org
www.aqvs.org
www.qavs.org
www.wvs.org
www.awvs.org
www.wavs.org
www.svs.org
www.asvs.org
www.savs.org
www.zvs.org
www.azvs.org
www.zavs.org
www.as.org
www.acs.org
www.avcs.org
www.acvs.org
www.afs.org
www.avfs.org
www.afvs.org
www.ags.org
www.avgs.org
www.agvs.org
www.abs.org
www.avbs.org
www.abvs.org
www.av.org
www.avw.org
www.avsw.org
www.avws.org
www.ave.org
www.avse.org
www.aves.org
www.avd.org
www.avsd.org
www.avds.org
www.avz.org
www.avsz.org
www.avzs.org
www.avx.org
www.avsx.org
www.avxs.org
www.ava.org
www.avsa.org
www.avas.org