Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

petitcoquin.net

フランス雑貨ショップ  ピローヌ・ジャポン

Page Load Speed

12.1 sec in total

First Response

2.9 sec

Resources Loaded

8.9 sec

Page Rendered

345 ms

petitcoquin.net screenshot

About Website

Visit petitcoquin.net now to see the best up-to-date Petitcoquin content and also check out these interesting facts you probably never knew about petitcoquin.net

Pylones Japon(ピローヌ ジャポン)は フランスのデザイン雑貨ブランド 「PYLONES」の日本総代理店です。大人気のガラスのリングやアクセサリーをはじめ、個性的で独創性のあるデザイン雑貨を取り扱っております。

Visit petitcoquin.net

Key Findings

We analyzed Petitcoquin.net page load time and found that the first response time was 2.9 sec and then it took 9.3 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

petitcoquin.net performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.4 s

0/100

10%

LCP (Largest Contentful Paint)

Value19.2 s

0/100

25%

SI (Speed Index)

Value11.3 s

5/100

10%

TBT (Total Blocking Time)

Value700 ms

43/100

30%

CLS (Cumulative Layout Shift)

Value0.568

12/100

15%

TTI (Time to Interactive)

Value40.1 s

0/100

10%

Network Requests Diagram

petitcoquin.net

2855 ms

default_pcsite.css

770 ms

top2.css

644 ms

top_slide.css

744 ms

jquery.min.js

2233 ms

Our browser made a total of 145 requests to load all elements on the main page. We found that 70% of them (101 requests) were addressed to the original Petitcoquin.net, 22% (32 requests) were made to Image1.shopserve.jp and 5% (7 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (3.2 sec) relates to the external source Image1.shopserve.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 300.5 kB (21%)

Content Size

1.4 MB

After Optimization

1.1 MB

In fact, the total size of Petitcoquin.net main page is 1.4 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 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 50.9 kB

  • Original 60.7 kB
  • After minification 53.7 kB
  • After compression 9.9 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.1 kB, which is 12% 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 50.9 kB or 84% of the original size.

Image Optimization

-10%

Potential reduce by 115.2 kB

  • Original 1.2 MB
  • After minification 1.0 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. Petitcoquin images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 113.2 kB

  • Original 189.5 kB
  • After minification 182.7 kB
  • After compression 76.3 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 113.2 kB or 60% of the original size.

CSS Optimization

-78%

Potential reduce by 21.2 kB

  • Original 27.1 kB
  • After minification 23.8 kB
  • After compression 5.8 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. Petitcoquin.net needs all CSS files to be minified and compressed as it can save up to 21.2 kB or 78% of the original size.

Requests Breakdown

Number of requests can be reduced by 40 (28%)

Requests Now

141

After Optimization

101

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

Accessibility Review

petitcoquin.net accessibility score

84

Accessibility Issues

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.

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

petitcoquin.net 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

petitcoquin.net SEO score

77

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

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    EUC-JP

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Petitcoquin.net 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 Petitcoquin.net main page’s claimed encoding is euc-jp. 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 Petitcoquin. 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: