Report Summary

  • 40

    Performance

    Renders faster than
    59% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 94

    SEO

    Google-friendlier than
    90% of websites

mori.com

Food Technology - Mori formerly Cambridge Crops, Boston

Page Load Speed

2.4 sec in total

First Response

370 ms

Resources Loaded

1.9 sec

Page Rendered

121 ms

mori.com screenshot

About Website

Click here to check amazing Mori content for United States. Otherwise, check out these important facts you probably never knew about mori.com

Mori formerly Cambridge Crops manufactures all-natural protective layer to slow down the spoiling process of food and keep fresher food for longer.

Visit mori.com

Key Findings

We analyzed Mori.com page load time and found that the first response time was 370 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

mori.com performance score

40

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

24/100

10%

LCP (Largest Contentful Paint)

Value10.5 s

0/100

25%

SI (Speed Index)

Value6.7 s

36/100

10%

TBT (Total Blocking Time)

Value450 ms

62/100

30%

CLS (Cumulative Layout Shift)

Value0.095

91/100

15%

TTI (Time to Interactive)

Value12.5 s

14/100

10%

Network Requests Diagram

mori.com

370 ms

Noto+Serif.css.8bacabd5ec4a4c1ad5ba0947fbc51ed9

425 ms

Open+Sans.css.7dec56fcda8f0be25585501a3297c0dd

404 ms

vendor.js.8b21b9097521067c7a1652f36d5cee4b

593 ms

appSecure.js.2cf5585e78f37873ea9c546ab1d538ea

278 ms

Our browser made a total of 18 requests to load all elements on the main page. We found that 28% of them (5 requests) were addressed to the original Mori.com, 50% (9 requests) were made to Content.mori.com and 6% (1 request) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (674 ms) belongs to the original domain Mori.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 284.1 kB (67%)

Content Size

421.8 kB

After Optimization

137.8 kB

In fact, the total size of Mori.com main page is 421.8 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. 20% of websites need less resources to load. Javascripts take 399.1 kB which makes up the majority of the site volume.

HTML Optimization

-67%

Potential reduce by 12.3 kB

  • Original 18.3 kB
  • After minification 18.2 kB
  • After compression 6.0 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 12.3 kB or 67% of the original size.

JavaScript Optimization

-67%

Potential reduce by 268.1 kB

  • Original 399.1 kB
  • After minification 372.4 kB
  • After compression 131.0 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 268.1 kB or 67% of the original size.

CSS Optimization

-82%

Potential reduce by 3.6 kB

  • Original 4.4 kB
  • After minification 2.2 kB
  • After compression 789 B

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. Mori.com needs all CSS files to be minified and compressed as it can save up to 3.6 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 4 (36%)

Requests Now

11

After Optimization

7

The browser has sent 11 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 5 to 1 for JavaScripts and as a result speed up the page load time.

Accessibility Review

mori.com accessibility score

100

Accessibility Issues

Best Practices

mori.com best practices score

83

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

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

mori.com SEO score

94

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

High

Tap targets are not sized appropriately

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.com 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.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 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: