Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

tpr.jp

The PARKSIDE ROOM 吉祥寺|メガネのSELECT SHOP

Page Load Speed

11.3 sec in total

First Response

580 ms

Resources Loaded

9 sec

Page Rendered

1.8 sec

tpr.jp screenshot

About Website

Visit tpr.jp now to see the best up-to-date Tpr content and also check out these interesting facts you probably never knew about tpr.jp

O-O 吉祥寺駅徒歩5分、井の頭公園近くの眼鏡(メガネ)・サングラス中心のショップ。Lunor / OLIVER PEOPLES / ayame / Oliver Goldsmith / COMESANDGOESなど国内外のブランドをセレクトしています。

Visit tpr.jp

Key Findings

We analyzed Tpr.jp page load time and found that the first response time was 580 ms and then it took 10.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

tpr.jp performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.8 s

5/100

10%

LCP (Largest Contentful Paint)

Value11.1 s

0/100

25%

SI (Speed Index)

Value13.9 s

1/100

10%

TBT (Total Blocking Time)

Value1,640 ms

12/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value29.3 s

0/100

10%

Network Requests Diagram

tpr.jp

580 ms

www.tpr.jp

3023 ms

index.js

524 ms

style.css

741 ms

analytics.js

413 ms

Our browser made a total of 110 requests to load all elements on the main page. We found that 96% of them (106 requests) were addressed to the original Tpr.jp, 2% (2 requests) were made to Google-analytics.com and 2% (2 requests) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (3 sec) belongs to the original domain Tpr.jp.

Page Optimization Overview & Recommendations

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

Content Size

322.6 kB

After Optimization

108.0 kB

In fact, the total size of Tpr.jp main page is 322.6 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. 80% 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. Javascripts take 193.3 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 71.1 kB

  • Original 81.3 kB
  • After minification 74.6 kB
  • After compression 10.2 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 71.1 kB or 87% of the original size.

Image Optimization

-14%

Potential reduce by 3.4 kB

  • Original 24.4 kB
  • After minification 21.0 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. Obviously, Tpr needs image optimization as it can save up to 3.4 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-62%

Potential reduce by 120.5 kB

  • Original 193.3 kB
  • After minification 178.0 kB
  • After compression 72.8 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 120.5 kB or 62% of the original size.

CSS Optimization

-83%

Potential reduce by 19.6 kB

  • Original 23.6 kB
  • After minification 20.8 kB
  • After compression 4.0 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. Tpr.jp needs all CSS files to be minified and compressed as it can save up to 19.6 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 3 (3%)

Requests Now

107

After Optimization

104

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

Accessibility Review

tpr.jp accessibility score

100

Accessibility Issues

Best Practices

tpr.jp best practices score

75

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

High

Page has valid source maps

SEO Factors

tpr.jp 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

    EN

  • Language Claimed

    JA

  • Encoding

    UTF-8

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