Report Summary

  • 2

    Performance

    Renders faster than
    19% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 0

    Best Practices

  • 83

    SEO

    Google-friendlier than
    46% of websites

paulbocuse.jp

株式会社ひらまつ

Page Load Speed

1.2 sec in total

First Response

531 ms

Resources Loaded

537 ms

Page Rendered

115 ms

paulbocuse.jp screenshot

About Website

Welcome to paulbocuse.jp homepage info - get ready to check Paulbocuse best content for Japan right away, or after learning these important things about paulbocuse.jp

株式会社ひらまつが展開するレストラン・ウエディング・ホテル・料亭・ワインのオンライン販売の各事業の情報を紹介します。

Visit paulbocuse.jp

Key Findings

We analyzed Paulbocuse.jp page load time and found that the first response time was 531 ms and then it took 652 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.

Performance Metrics

paulbocuse.jp performance score

2

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

9/100

10%

LCP (Largest Contentful Paint)

Value20.1 s

0/100

25%

SI (Speed Index)

Value12.4 s

3/100

10%

TBT (Total Blocking Time)

Value4,890 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.893

3/100

15%

TTI (Time to Interactive)

Value84.0 s

0/100

10%

Network Requests Diagram

paulbocuse.jp

531 ms

Our browser made a total of 1 request to load all elements on the main page. We found that all of those requests were addressed to Paulbocuse.jp and no external sources were called. The less responsive or slowest element that took the longest time to load (531 ms) belongs to the original domain Paulbocuse.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 104 B (30%)

Content Size

342 B

After Optimization

238 B

In fact, the total size of Paulbocuse.jp main page is 342 B. This result falls within the top 5000 of lightweight and thus fast loading web pages. Only a small number of websites need less resources to load. HTML takes 342 B which makes up the majority of the site volume.

HTML Optimization

-30%

Potential reduce by 104 B

  • Original 342 B
  • After minification 340 B
  • After compression 238 B

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 104 B or 30% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

0

After Optimization

0

Besides the initial HTML request, no CSS, Javascripts, AJAX or image files were requested in the course of web page rendering.

Accessibility Review

paulbocuse.jp accessibility score

83

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA input fields do not have accessible names

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

SEO Factors

paulbocuse.jp SEO score

83

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

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 doesn't use legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Paulbocuse.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Paulbocuse.jp main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

Open Graph description is not detected on the main page of Paulbocuse. 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: