Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 69

    Accessibility

    Visual factors better than
    that of 34% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

omoda.com

The fashion boutique that loves you back | Omoda

Page Load Speed

2.4 sec in total

First Response

439 ms

Resources Loaded

1.2 sec

Page Rendered

782 ms

omoda.com screenshot

About Website

Visit omoda.com now to see the best up-to-date Omoda content for Japan and also check out these interesting facts you probably never knew about omoda.com

Jouw nieuwe kleding, schoenen, tassen en accessoires van 250+ merken vind je bij Omoda. ✓ 30 dagen retour ✓ Gratis bezorging en retour* ✓ Achteraf betalen

Visit omoda.com

Key Findings

We analyzed Omoda.com page load time and found that the first response time was 439 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

omoda.com performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

67/100

10%

LCP (Largest Contentful Paint)

Value8.1 s

2/100

25%

SI (Speed Index)

Value7.8 s

24/100

10%

TBT (Total Blocking Time)

Value1,300 ms

18/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value11.9 s

17/100

10%

Network Requests Diagram

www.omoda.nl

439 ms

j.php

279 ms

lazysizes-5.2.2.min.js

151 ms

gtm.js

152 ms

global.css

61 ms

Our browser made a total of 51 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Omoda.com, 8% (4 requests) were made to Dev.visualwebsiteoptimizer.com and 2% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (439 ms) relates to the external source Omoda.nl.

Page Optimization Overview & Recommendations

Page size can be reduced by 472.4 kB (25%)

Content Size

1.9 MB

After Optimization

1.4 MB

In fact, the total size of Omoda.com main page is 1.9 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 472.3 kB

  • Original 521.4 kB
  • After minification 423.9 kB
  • After compression 49.1 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. This page needs HTML code to be minified as it can gain 97.5 kB, which is 19% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 472.3 kB or 91% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 1.0 MB
  • After minification 1.0 MB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Omoda images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 158 B

  • Original 278.3 kB
  • After minification 278.3 kB
  • After compression 278.1 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 78.5 kB
  • After minification 78.5 kB
  • After compression 78.5 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Omoda.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 25 (57%)

Requests Now

44

After Optimization

19

The browser has sent 44 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Omoda. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

omoda.com accessibility score

69

Accessibility Issues

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.

Impact

Issue

High

[aria-*] attributes do not match their roles

High

[role]s are not contained by their required parent element

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending 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.

Impact

Issue

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

omoda.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

omoda.com SEO score

86

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    NL

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Omoda.com can be misinterpreted by Google and other search engines. Our service has detected that Dutch is used on the page, and it does not match the claimed English language. Our system also found out that Omoda.com main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

Open Graph description is not detected on the main page of Omoda. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: