Report Summary

  • 20

    Performance

    Renders faster than
    38% 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

abysse.jp

abysse | modern seafood cuisine in daikanyama tokyo

Page Load Speed

6 sec in total

First Response

519 ms

Resources Loaded

4.5 sec

Page Rendered

988 ms

abysse.jp screenshot

About Website

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

modern seafood cuisine restaurants in Tokyo Japan. Abysse will strive for customers who love modern seafood cuisine and wine from heart. Owner and chef Kotaro Meguro worked under two Michelin three-st...

Visit abysse.jp

Key Findings

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

Performance Metrics

abysse.jp performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

19/100

10%

LCP (Largest Contentful Paint)

Value19.1 s

0/100

25%

SI (Speed Index)

Value8.5 s

18/100

10%

TBT (Total Blocking Time)

Value3,780 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value15.4 s

7/100

10%

Network Requests Diagram

abysse.jp

519 ms

abysse.jp

747 ms

vendor.css

176 ms

main.css

355 ms

modernizr.js

559 ms

Our browser made a total of 35 requests to load all elements on the main page. We found that 77% of them (27 requests) were addressed to the original Abysse.jp, 11% (4 requests) were made to Fonts.gstatic.com and 6% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Abysse.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 38.5 kB (1%)

Content Size

5.1 MB

After Optimization

5.0 MB

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

HTML Optimization

-81%

Potential reduce by 36.3 kB

  • Original 44.8 kB
  • After minification 37.8 kB
  • After compression 8.5 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. This page needs HTML code to be minified as it can gain 7.0 kB, which is 16% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 36.3 kB or 81% of the original size.

Image Optimization

-0%

Potential reduce by 46 B

  • Original 4.9 MB
  • After minification 4.9 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. Abysse images are well optimized though.

JavaScript Optimization

-3%

Potential reduce by 2.1 kB

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

-0%

Potential reduce by 31 B

  • Original 9.7 kB
  • After minification 9.7 kB
  • After compression 9.6 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. Abysse.jp has all CSS files already compressed.

Requests Breakdown

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

Requests Now

27

After Optimization

23

The browser has sent 27 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Abysse. 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

abysse.jp accessibility score

100

Accessibility Issues

Best Practices

abysse.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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

abysse.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 Abysse.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 Abysse.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 Abysse. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: