Puu.la Test Results
Puu.la Mobile Performance: 55/100
Quick overview:
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Reduce initial server response time
Root document took 700 ms
Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.
Avoid multiple page redirects
Potential savings of 1,240 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Largest Contentful Paint element
6,620 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Minimize main-thread work
2.5 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work
Reduce unused CSS
Potential savings of 44 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.
Reduce JavaScript execution time
1.3 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.
Reduce unused JavaScript
Potential savings of 163 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.
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
Serve static assets with an efficient cache policy
16 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Avoid serving legacy JavaScript to modern browsers
Potential savings of 6 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn how to use modern JavaScript
Properly size images
Potential savings of 5 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
Defer offscreen images
Potential savings of 7 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn how to defer offscreen images.
Max Potential First Input Delay
270 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.
First Meaningful Paint
3.8 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric.
Time to Interactive
6.7 s
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.
Puu.la Mobile SEO: 100/100
Quick overview:
Puu.la Mobile Best Practices: 83/100
Quick overview:
General
Missing source maps for large first-party JavaScript
Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.
Trust and Safety
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 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.
Puu.la Mobile Accessibility: 68/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.
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 how to make links accessible.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
`<html>` element does not have a `[lang]` attribute
If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
`[aria-*]` attributes do not match their roles
Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.
Elements use prohibited ARIA attributes
Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.
`[aria-*]` attributes do not have valid values
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.
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.
Best practices
These items highlight common accessibility best practices.
Touch targets do not have sufficient size or spacing.
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
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 how to provide sufficient color contrast.
Similar sites
Similar tests
www.puu.com
www.puu.net
www.puu.org
www.puu.info
www.puu.biz
www.puu.us
www.puu.mobi
www.uu.la
www.puu.la
www.ouu.la
www.pouu.la
www.opuu.la
www.luu.la
www.pluu.la
www.lpuu.la
www.pu.la
www.pyu.la
www.puyu.la
www.pyuu.la
www.phu.la
www.puhu.la
www.phuu.la
www.pju.la
www.puju.la
www.pjuu.la
www.piu.la
www.puiu.la
www.piuu.la
www.puy.la
www.puuy.la
www.puh.la
www.puuh.la
www.puj.la
www.puuj.la
www.pui.la
www.puui.la
www.puu.net
www.puu.org
www.puu.info
www.puu.biz
www.puu.us
www.puu.mobi
www.uu.la
www.puu.la
www.ouu.la
www.pouu.la
www.opuu.la
www.luu.la
www.pluu.la
www.lpuu.la
www.pu.la
www.pyu.la
www.puyu.la
www.pyuu.la
www.phu.la
www.puhu.la
www.phuu.la
www.pju.la
www.puju.la
www.pjuu.la
www.piu.la
www.puiu.la
www.piuu.la
www.puy.la
www.puuy.la
www.puh.la
www.puuh.la
www.puj.la
www.puuj.la
www.pui.la
www.puui.la