Report Summary

  • 59

    Performance

    Renders faster than
    74% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 62

    SEO

    Google-friendlier than
    23% of websites

matilda.co.jp

Matilda

Page Load Speed

9.6 sec in total

First Response

2.2 sec

Resources Loaded

7.2 sec

Page Rendered

280 ms

About Website

Welcome to matilda.co.jp homepage info - get ready to check Matilda best content right away, or after learning these important things about matilda.co.jp

目黒区青葉台(中目黒)にあるフラワーショップ「Matilda」のオフィシャルサイトです。こだわり抜いた花や洗練された花器、インパクトあるアレンジメント、ブーケなどをお届けします。

Visit matilda.co.jp

Key Findings

We analyzed Matilda.co.jp page load time and found that the first response time was 2.2 sec and then it took 7.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

matilda.co.jp performance score

59

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

65/100

10%

LCP (Largest Contentful Paint)

Value27.9 s

0/100

25%

SI (Speed Index)

Value8.6 s

17/100

10%

TBT (Total Blocking Time)

Value120 ms

97/100

30%

CLS (Cumulative Layout Shift)

Value0.01

100/100

15%

TTI (Time to Interactive)

Value5.7 s

69/100

10%

Network Requests Diagram

matilda.co.jp

2191 ms

css

18 ms

css

34 ms

style.css

343 ms

jquery.bxslider.css

331 ms

Our browser made a total of 52 requests to load all elements on the main page. We found that 62% of them (32 requests) were addressed to the original Matilda.co.jp, 23% (12 requests) were made to I.pinimg.com and 4% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (4.5 sec) belongs to the original domain Matilda.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 176.3 kB (4%)

Content Size

4.0 MB

After Optimization

3.9 MB

In fact, the total size of Matilda.co.jp main page is 4.0 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. 30% of websites need less resources to load. Images take 3.9 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 27.4 kB

  • Original 31.9 kB
  • After minification 29.5 kB
  • After compression 4.6 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 27.4 kB or 86% of the original size.

Image Optimization

-3%

Potential reduce by 132.6 kB

  • Original 3.9 MB
  • After minification 3.8 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. Matilda images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 50 B

  • Original 54.4 kB
  • After minification 54.4 kB
  • After compression 54.4 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

-79%

Potential reduce by 16.3 kB

  • Original 20.6 kB
  • After minification 17.4 kB
  • After compression 4.3 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. Matilda.co.jp needs all CSS files to be minified and compressed as it can save up to 16.3 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (27%)

Requests Now

49

After Optimization

36

The browser has sent 49 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Matilda. 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 from 4 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

matilda.co.jp accessibility score

76

Accessibility Issues

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

Best Practices

matilda.co.jp 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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

matilda.co.jp SEO score

62

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

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Matilda.co.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it matches the claimed language. Our system also found out that Matilda.co.jp 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 data is detected on the main page of Matilda. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: