Report Summary

  • 41

    Performance

    Renders faster than
    60% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

Page Load Speed

4.4 sec in total

First Response

904 ms

Resources Loaded

3.2 sec

Page Rendered

306 ms

prologue-mitaka.com screenshot

About Website

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

ミシュラン,ブリヂストン,ルッチーニ,コンチネンタル,ピレリ,ミタカ,東京,三鷹,タイヤ,プロショップ

Visit prologue-mitaka.com

Key Findings

We analyzed Prologue-mitaka.com page load time and found that the first response time was 904 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

prologue-mitaka.com performance score

41

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.4 s

0/100

10%

LCP (Largest Contentful Paint)

Value11.2 s

0/100

25%

SI (Speed Index)

Value11.1 s

6/100

10%

TBT (Total Blocking Time)

Value310 ms

78/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value10.3 s

24/100

10%

Network Requests Diagram

prologue-mitaka.com

904 ms

reset.css

184 ms

common.css

317 ms

jquery.min.js

32 ms

smoothscroll.js

315 ms

Our browser made a total of 57 requests to load all elements on the main page. We found that 93% of them (53 requests) were addressed to the original Prologue-mitaka.com, 4% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Prologue-mitaka.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 193.2 kB (20%)

Content Size

957.0 kB

After Optimization

763.8 kB

In fact, the total size of Prologue-mitaka.com main page is 957.0 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. Images take 751.9 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 13.1 kB

  • Original 17.8 kB
  • After minification 16.9 kB
  • After compression 4.7 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 13.1 kB or 74% of the original size.

Image Optimization

-6%

Potential reduce by 43.3 kB

  • Original 751.9 kB
  • After minification 708.6 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. Prologue Mitaka images are well optimized though.

JavaScript Optimization

-72%

Potential reduce by 117.7 kB

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

CSS Optimization

-80%

Potential reduce by 19.2 kB

  • Original 24.1 kB
  • After minification 18.4 kB
  • After compression 4.9 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. Prologue-mitaka.com needs all CSS files to be minified and compressed as it can save up to 19.2 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (18%)

Requests Now

56

After Optimization

46

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

Accessibility Review

prologue-mitaka.com accessibility score

100

Accessibility Issues

Best Practices

prologue-mitaka.com 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

SEO Factors

prologue-mitaka.com SEO score

100

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

    TH

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Prologue-mitaka.com can be misinterpreted by Google and other search engines. Our service has detected that Thai is used on the page, and it does not match the claimed Japanese language. Our system also found out that Prologue-mitaka.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 Prologue Mitaka. 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: