Tools & Wizards About Us
pebeo.co.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

pebeo.co.jp

ペベオ・ジャポン株式会社 | Pebeo Japon

Page Load Speed

4.1 sec in total

First Response

592 ms

Resources Loaded

3.3 sec

Page Rendered

180 ms

pebeo.co.jp screenshot

About Website

Visit pebeo.co.jp now to see the best up-to-date Pebeo content for Japan and also check out these interesting facts you probably never knew about pebeo.co.jp

南フランス・プロヴァンスの絵具 美しい色彩であなたの暮らしをもっと素敵に

Visit pebeo.co.jp

Key Findings

We analyzed Pebeo.co.jp page load time and found that the first response time was 592 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

pebeo.co.jp performance score

0

Network Requests Diagram

pebeo.co.jp

592 ms

styles.css

518 ms

mt.js

546 ms

swfobject.js

313 ms

jquery-1.3.2.min.js

468 ms

Our browser made a total of 40 requests to load all elements on the main page. We found that 95% of them (38 requests) were addressed to the original Pebeo.co.jp, 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Pebeo.co.jp.

Page Optimization Overview & Recommendations

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

Content Size

694.8 kB

After Optimization

554.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pebeo.co.jp main page is 694.8 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. 25% of websites need less resources to load. Images take 514.0 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 12.4 kB

  • Original 15.4 kB
  • After minification 11.0 kB
  • After compression 3.1 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 4.4 kB, which is 29% 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 12.4 kB or 80% of the original size.

Image Optimization

-3%

Potential reduce by 17.1 kB

  • Original 514.0 kB
  • After minification 497.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. Pebeo images are well optimized though.

JavaScript Optimization

-59%

Potential reduce by 64.9 kB

  • Original 110.4 kB
  • After minification 99.0 kB
  • After compression 45.4 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 64.9 kB or 59% of the original size.

CSS Optimization

-84%

Potential reduce by 46.2 kB

  • Original 54.9 kB
  • After minification 44.3 kB
  • After compression 8.7 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. Pebeo.co.jp needs all CSS files to be minified and compressed as it can save up to 46.2 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 16 (41%)

Requests Now

39

After Optimization

23

  • Images
  • JavaScript
  • CSS

The browser has sent 39 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pebeo. 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 5 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

pebeo.co.jp

pebeo.co.jp

592 ms

styles.css

styles.css

518 ms

mt.js

mt.js

546 ms

swfobject.js

swfobject.js

313 ms

jquery-1.3.2.min.js

jquery-1.3.2.min.js

468 ms

jquery.url.js

jquery.url.js

332 ms

pebeo.js

pebeo.js

349 ms

reset.css

reset.css

331 ms

blog.css

blog.css

338 ms

screen.css

screen.css

357 ms

screen.css

screen.css

342 ms

banner_nakayama.jpg

banner_nakayama.jpg

318 ms

bg-container.jpg

bg-container.jpg

1094 ms

logo-header.gif

logo-header.gif

310 ms

description.gif

description.gif

315 ms

btn-home.gif

btn-home.gif

314 ms

btn-company.gif

btn-company.gif

314 ms

btn-france.gif

btn-france.gif

316 ms

news.png

news.png

621 ms

product.png

product.png

643 ms

shoplist.png

shoplist.png

642 ms

qa.png

qa.png

644 ms

contact.png

contact.png

653 ms

banner_setacolor.jpg

banner_setacolor.jpg

1276 ms

banner_mix02.jpg

banner_mix02.jpg

1295 ms

news.gif

news.gif

981 ms

news02.gif

news02.gif

995 ms

event.gif

event.gif

1006 ms

zushiplay.jpg

zushiplay.jpg

1620 ms

pac.jpg

pac.jpg

1499 ms

edubaner.jpg

edubaner.jpg

1501 ms

manta_banner.jpg

manta_banner.jpg

1760 ms

btn-totop.gif

btn-totop.gif

1588 ms

logo-footer.gif

logo-footer.gif

1626 ms

copyright.gif

copyright.gif

1809 ms

banner_f02.jpg

banner_f02.jpg

325 ms

btn-more.gif

btn-more.gif

330 ms

banner_youtube02.jpg

banner_youtube02.jpg

495 ms

ga.js

ga.js

8 ms

__utm.gif

__utm.gif

16 ms

SEO Factors

pebeo.co.jp SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pebeo.co.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 Pebeo.co.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

pebeo.co.jp

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