Jaub2.projets-web.net Site Title

Jaubalet Paris

Jaub2.projets-web.net Meta Description

Boutique propulsée par PrestaShop

Jaub2.projets-web.net Test Results

Jaub2.projets-web.net Mobile Performance: 64/100
Quick overview:
Duplicated JavaScript
Est savings of 146 KiB
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
LCP request discovery
Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading
Use efficient cache lifetimes
Est savings of 586 KiB
A long cache lifetime can speed up repeat visits to your page. Learn more.
Document request latency
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
Improve image delivery
Est savings of 301 KiB
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
Forced reflow
Many APIs, typically reading layout geometry, force the rendering engine to pause script execution in order to calculate the style and layout. Learn more about forced reflow and its mitigations.
Time to Interactive
7.2 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.
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Avoid multiple page redirects
Est savings of 1,130 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Largest Contentful Paint element
7,090 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Efficiently encode images
Est savings of 98 KiB
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.
Preload Largest Contentful Paint image
Est savings of 1,710 ms
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.
Serve images in next-gen formats
Est savings of 379 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more about modern image formats.
Reduce unused JavaScript
Est savings of 57 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.
Reduce initial server response time
Root document took 1,170 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.
Remove duplicate modules in JavaScript bundles
Est savings of 40 KiB
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers
Est savings of 0 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support legacy browsers. Learn why most sites can deploy ES6+ code without transpiling
Properly size images
Est savings of 13 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
Serve static assets with an efficient cache policy
17 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Defer offscreen images
Est savings of 215 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.
Avoid an excessive DOM size
1,779 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn how to avoid an excessive DOM size.

Jaub2.projets-web.net Mobile SEO: 38/100
Quick overview:
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Page is blocked from indexing
Search engines are unable to include your pages in search results if they don't have permission to crawl them. Learn more about crawler directives.
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Document does not have a valid `rel=canonical`
Canonical links suggest which URL to show in search results. Learn more about canonical links. Points to the domain's root URL (the homepage), instead of an equivalent page of content
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 about the `alt` attribute.
Links do not have descriptive text
1 link found
Descriptive link text helps search engines understand your content. Learn how to make links more accessible.
Document doesn't have a valid `hreflang`
hreflang links tell search engines what version of a page they should list in search results for a given language or region. Learn more about `hreflang`.

Jaub2.projets-web.net Mobile Best Practices: 79/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.
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 about this errors in console diagnostic audit
Jaub2.projets-web.net Mobile Accessibility: 76/100
Quick overview:
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.
`button`, `link`, and `menuitem` elements do not have accessible names.
When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to make command elements more accessible.
Navigation
These are opportunities to improve keyboard navigation in your application.
Some elements have a `[tabindex]` value greater than 0
A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.
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.
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.
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 about the `alt` attribute.
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.
Elements with visible text labels do not have matching accessible names.
Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.
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.
Similar tests
www.jaub2.com
www.jaub2.net
www.jaub2.org
www.jaub2.info
www.jaub2.biz
www.jaub2.us
www.jaub2.mobi
www.aub2.projets-web.net
www.jaub2.projets-web.net
www.naub2.projets-web.net
www.jnaub2.projets-web.net
www.njaub2.projets-web.net
www.haub2.projets-web.net
www.jhaub2.projets-web.net
www.hjaub2.projets-web.net
www.uaub2.projets-web.net
www.juaub2.projets-web.net
www.ujaub2.projets-web.net
www.iaub2.projets-web.net
www.jiaub2.projets-web.net
www.ijaub2.projets-web.net
www.kaub2.projets-web.net
www.jkaub2.projets-web.net
www.kjaub2.projets-web.net
www.maub2.projets-web.net
www.jmaub2.projets-web.net
www.mjaub2.projets-web.net
www.jub2.projets-web.net
www.jqub2.projets-web.net
www.jaqub2.projets-web.net
www.jqaub2.projets-web.net
www.jwub2.projets-web.net
www.jawub2.projets-web.net
www.jwaub2.projets-web.net
www.jsub2.projets-web.net
www.jasub2.projets-web.net
www.jsaub2.projets-web.net
www.jzub2.projets-web.net
www.jazub2.projets-web.net
www.jzaub2.projets-web.net
www.jab2.projets-web.net
www.jayb2.projets-web.net
www.jauyb2.projets-web.net
www.jayub2.projets-web.net
www.jahb2.projets-web.net
www.jauhb2.projets-web.net
www.jahub2.projets-web.net
www.jajb2.projets-web.net
www.jaujb2.projets-web.net
www.jajub2.projets-web.net
www.jaib2.projets-web.net
www.jauib2.projets-web.net
www.jaiub2.projets-web.net
www.jau2.projets-web.net
www.jauv2.projets-web.net
www.jaubv2.projets-web.net
www.jauvb2.projets-web.net
www.jaug2.projets-web.net
www.jaubg2.projets-web.net
www.jaugb2.projets-web.net
www.jauh2.projets-web.net
www.jaubh2.projets-web.net
www.jaun2.projets-web.net
www.jaubn2.projets-web.net
www.jaunb2.projets-web.net
www.jaub.projets-web.net
Last Tested: