Report Summary

  • 71

    Performance

    Renders faster than
    82% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

mori.london

mori.london - animated LED candles and decorative lamps

Page Load Speed

739 ms in total

First Response

76 ms

Resources Loaded

608 ms

Page Rendered

55 ms

mori.london screenshot

About Website

Welcome to mori.london homepage info - get ready to check Mori best content right away, or after learning these important things about mori.london

mori.london produces animated LED candles and oil lamps in beautifully designed and hand crafted glass enclosures.

Visit mori.london

Key Findings

We analyzed Mori.london page load time and found that the first response time was 76 ms and then it took 663 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.

Performance Metrics

mori.london performance score

71

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

83/100

10%

LCP (Largest Contentful Paint)

Value3.9 s

51/100

25%

SI (Speed Index)

Value2.8 s

96/100

10%

TBT (Total Blocking Time)

Value350 ms

73/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value9.0 s

34/100

10%

Network Requests Diagram

www.mori.london

76 ms

originTrials.41d7301a.bundle.min.js

36 ms

minified.js

41 ms

focus-within-polyfill.js

40 ms

polyfill.min.js

35 ms

Our browser made a total of 27 requests to load all elements on the main page. We found that 4% of them (1 request) were addressed to the original Mori.london, 41% (11 requests) were made to Sentry-next.wixpress.com and 41% (11 requests) were made to Static.parastorage.com. The less responsive or slowest element that took the longest time to load (394 ms) relates to the external source App-api.vidjet.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 279.0 kB (48%)

Content Size

582.7 kB

After Optimization

303.8 kB

In fact, the total size of Mori.london main page is 582.7 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 35% of websites need less resources to load. HTML takes 356.0 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 276.2 kB

  • Original 356.0 kB
  • After minification 354.3 kB
  • After compression 79.8 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 276.2 kB or 78% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 3.3 kB
  • After minification 3.3 kB

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. Mori images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 2.8 kB

  • Original 223.4 kB
  • After minification 223.4 kB
  • After compression 220.6 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.

Requests Breakdown

Number of requests can be reduced by 11 (79%)

Requests Now

14

After Optimization

3

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

Accessibility Review

mori.london accessibility score

98

Accessibility Issues

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.

Best Practices

mori.london best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

mori.london SEO score

93

Search Engine Optimization Advices

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mori.london can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Mori.london 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 Mori. 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: