Feraud.paris Site Title
Féraud Fashion Shop – Die Eleganz der Pariser Couture | Rösch-Fashion
Feraud.paris Meta Description
Rösch Fashion Onlineshop für qualitativ hochwertige Nachtwäsche ✓ Nachhaltig produzierte Mode ✓ Versandkostenfrei in DE shoppen!
Feraud.paris Test Results
Feraud.paris Mobile Performance: 41/100
Quick overview:
Time to Interactive
35.0 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.
Max Potential First Input Delay
220 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.
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Avoid an excessive DOM size
4,104 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.
Minimize main-thread work
5.0 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 JavaScript execution time
2.7 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.
Largest Contentful Paint element
33,350 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Reduce unused JavaScript
Potential savings of 106 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.
Defer offscreen images
Potential savings of 376 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 multiple page redirects
Potential savings of 1,830 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Eliminate render-blocking resources
Potential savings of 5,400 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn how to eliminate render-blocking resources.
Reduce unused CSS
Potential savings of 93 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.
Properly size images
Potential savings of 605 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
Some third-party resources can be lazy loaded with a facade
1 facade alternative available
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn how to defer third-parties with a facade.
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`.
Serve static assets with an efficient cache policy
7 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
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
Avoid enormous network payloads
Total size was 9,697 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Avoid serving legacy JavaScript to modern browsers
Potential savings of 7 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
Feraud.paris Mobile SEO: 69/100
Quick overview:
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s 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.
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
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.
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
Feraud.paris Mobile Best Practices: 76/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 how to provide responsive images.
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.
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.
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
Feraud.paris Mobile Accessibility: 70/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.
Uses ARIA roles on incompatible elements
Many HTML elements can only be assigned certain ARIA roles. Using ARIA roles where they are not allowed can interfere with the accessibility of the web page. Learn more about ARIA roles.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` are missing some or all of those required children.
Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.
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.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
List items (`<li>`) are not contained within `<ul>`, `<ol>` or `<menu>` parent elements.
Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.
Lists do not contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.
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.
Form elements do not have associated labels
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.
Contrast
These are opportunities to improve the legibility of your content.
Links rely on color to be distinguishable.
Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.
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 tests
www.feraud.com
www.feraud.net
www.feraud.org
www.feraud.info
www.feraud.biz
www.feraud.us
www.feraud.mobi
www.eraud.paris
www.feraud.paris
www.ceraud.paris
www.fceraud.paris
www.cferaud.paris
www.deraud.paris
www.fderaud.paris
www.dferaud.paris
www.reraud.paris
www.freraud.paris
www.rferaud.paris
www.teraud.paris
www.fteraud.paris
www.tferaud.paris
www.geraud.paris
www.fgeraud.paris
www.gferaud.paris
www.veraud.paris
www.fveraud.paris
www.vferaud.paris
www.fraud.paris
www.fwraud.paris
www.fewraud.paris
www.fweraud.paris
www.fsraud.paris
www.fesraud.paris
www.fseraud.paris
www.fdraud.paris
www.fedraud.paris
www.frraud.paris
www.ferraud.paris
www.feaud.paris
www.feeaud.paris
www.fereaud.paris
www.feeraud.paris
www.fedaud.paris
www.ferdaud.paris
www.fefaud.paris
www.ferfaud.paris
www.fefraud.paris
www.fetaud.paris
www.fertaud.paris
www.fetraud.paris
www.ferud.paris
www.ferqud.paris
www.feraqud.paris
www.ferqaud.paris
www.ferwud.paris
www.ferawud.paris
www.ferwaud.paris
www.fersud.paris
www.ferasud.paris
www.fersaud.paris
www.ferzud.paris
www.ferazud.paris
www.ferzaud.paris
www.ferad.paris
www.ferayd.paris
www.ferauyd.paris
www.ferayud.paris
www.ferahd.paris
www.ferauhd.paris
www.ferahud.paris
www.ferajd.paris
www.feraujd.paris
www.ferajud.paris
www.feraid.paris
www.ferauid.paris
www.feraiud.paris
www.ferau.paris
www.feraux.paris
www.feraudx.paris
www.ferauxd.paris
www.feraus.paris
www.ferauds.paris
www.ferausd.paris
www.feraue.paris
www.feraude.paris
www.feraued.paris
www.feraur.paris
www.feraudr.paris
www.feraurd.paris
www.ferauf.paris
www.feraudf.paris
www.feraufd.paris
www.ferauc.paris
www.feraudc.paris
www.feraucd.paris
www.feraud.net
www.feraud.org
www.feraud.info
www.feraud.biz
www.feraud.us
www.feraud.mobi
www.eraud.paris
www.feraud.paris
www.ceraud.paris
www.fceraud.paris
www.cferaud.paris
www.deraud.paris
www.fderaud.paris
www.dferaud.paris
www.reraud.paris
www.freraud.paris
www.rferaud.paris
www.teraud.paris
www.fteraud.paris
www.tferaud.paris
www.geraud.paris
www.fgeraud.paris
www.gferaud.paris
www.veraud.paris
www.fveraud.paris
www.vferaud.paris
www.fraud.paris
www.fwraud.paris
www.fewraud.paris
www.fweraud.paris
www.fsraud.paris
www.fesraud.paris
www.fseraud.paris
www.fdraud.paris
www.fedraud.paris
www.frraud.paris
www.ferraud.paris
www.feaud.paris
www.feeaud.paris
www.fereaud.paris
www.feeraud.paris
www.fedaud.paris
www.ferdaud.paris
www.fefaud.paris
www.ferfaud.paris
www.fefraud.paris
www.fetaud.paris
www.fertaud.paris
www.fetraud.paris
www.ferud.paris
www.ferqud.paris
www.feraqud.paris
www.ferqaud.paris
www.ferwud.paris
www.ferawud.paris
www.ferwaud.paris
www.fersud.paris
www.ferasud.paris
www.fersaud.paris
www.ferzud.paris
www.ferazud.paris
www.ferzaud.paris
www.ferad.paris
www.ferayd.paris
www.ferauyd.paris
www.ferayud.paris
www.ferahd.paris
www.ferauhd.paris
www.ferahud.paris
www.ferajd.paris
www.feraujd.paris
www.ferajud.paris
www.feraid.paris
www.ferauid.paris
www.feraiud.paris
www.ferau.paris
www.feraux.paris
www.feraudx.paris
www.ferauxd.paris
www.feraus.paris
www.ferauds.paris
www.ferausd.paris
www.feraue.paris
www.feraude.paris
www.feraued.paris
www.feraur.paris
www.feraudr.paris
www.feraurd.paris
www.ferauf.paris
www.feraudf.paris
www.feraufd.paris
www.ferauc.paris
www.feraudc.paris
www.feraucd.paris