Tools & Wizards About Us
purezento.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

purezento.jp

|

Page Load Speed

5.4 sec in total

First Response

1 sec

Resources Loaded

3.9 sec

Page Rendered

462 ms

purezento.jp screenshot

About Website

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

偉人の名言にふれて英単語や英会話を学びましょう。

Visit purezento.jp

Key Findings

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

Performance Metrics

purezento.jp performance score

0

Network Requests Diagram

purezento.jp

1023 ms

wp-emoji-release.min.js

674 ms

styles.css,qver=4.4.pagespeed.ce.fIjaP8m3jJ.css

348 ms

base.css,qver=4.4.2.pagespeed.ce.CptsbAUaSa.css

711 ms

rwd.css,qver=4.4.2.pagespeed.ce.AG7WdqmJkn.css

372 ms

Our browser made a total of 39 requests to load all elements on the main page. We found that 85% of them (33 requests) were addressed to the original Purezento.jp, 8% (3 requests) were made to Google-analytics.com and 3% (1 request) were made to Statics.a8.net. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Purezento.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 311.3 kB (38%)

Content Size

811.9 kB

After Optimization

500.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-77%

Potential reduce by 32.1 kB

  • Original 42.0 kB
  • After minification 41.8 kB
  • After compression 9.8 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 32.1 kB or 77% of the original size.

Image Optimization

-0%

Potential reduce by 59 B

  • Original 399.1 kB
  • After minification 399.1 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. Purezento images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 142.3 kB

  • Original 216.4 kB
  • After minification 216.3 kB
  • After compression 74.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 142.3 kB or 66% of the original size.

CSS Optimization

-89%

Potential reduce by 136.8 kB

  • Original 154.4 kB
  • After minification 122.5 kB
  • After compression 17.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. Purezento.jp needs all CSS files to be minified and compressed as it can save up to 136.8 kB or 89% of the original size.

Requests Breakdown

Number of requests can be reduced by 21 (57%)

Requests Now

37

After Optimization

16

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

purezento.jp

purezento.jp

1023 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

674 ms

styles.css,qver=4.4.pagespeed.ce.fIjaP8m3jJ.css

styles.css,qver=4.4.pagespeed.ce.fIjaP8m3jJ.css

348 ms

base.css,qver=4.4.2.pagespeed.ce.CptsbAUaSa.css

base.css,qver=4.4.2.pagespeed.ce.CptsbAUaSa.css

711 ms

rwd.css,qver=4.4.2.pagespeed.ce.AG7WdqmJkn.css

rwd.css,qver=4.4.2.pagespeed.ce.AG7WdqmJkn.css

372 ms

wpp.css,qver=3.3.3.pagespeed.ce.ZUwz9rjzGg.css

wpp.css,qver=3.3.3.pagespeed.ce.ZUwz9rjzGg.css

374 ms

jquery.js,qver=1.11.3.pagespeed.jm.zixJPNMRNN.js

jquery.js,qver=1.11.3.pagespeed.jm.zixJPNMRNN.js

961 ms

jquery-migrate.min.js,qver=1.2.1.pagespeed.jm.mhpNjdU8Wl.js

jquery-migrate.min.js,qver=1.2.1.pagespeed.jm.mhpNjdU8Wl.js

522 ms

plugin.css

plugin.css

558 ms

datatables.css

datatables.css

558 ms

ad.js

ad.js

33 ms

jquery.form.min.js,qver=3.51.0-2014.06.20.pagespeed.jm.RVBOol6lkO.js

jquery.form.min.js,qver=3.51.0-2014.06.20.pagespeed.jm.RVBOol6lkO.js

717 ms

scripts.js,qver=4.4.pagespeed.jm.iZTDISK5pG.js

scripts.js,qver=4.4.pagespeed.jm.iZTDISK5pG.js

595 ms

utility.js,qver=4.4.2.pagespeed.jm.8Yg99QAmgY.js

utility.js,qver=4.4.2.pagespeed.jm.8Yg99QAmgY.js

593 ms

analytics.js

analytics.js

76 ms

header-border.png

header-border.png

225 ms

35968890e98ef78a3e6b6de4d9f44347.png.pagespeed.ce.4tsMs4wNBQ.png

35968890e98ef78a3e6b6de4d9f44347.png.pagespeed.ce.4tsMs4wNBQ.png

869 ms

midashi-h1.png

midashi-h1.png

227 ms

246x200xc8fab761e038bdbca266901e69bf1cb3-246x200.png.pagespeed.ic.zjEcGeRZ56.jpg

246x200xc8fab761e038bdbca266901e69bf1cb3-246x200.png.pagespeed.ic.zjEcGeRZ56.jpg

355 ms

icon-arw-next.png

icon-arw-next.png

227 ms

246x81x2016-02-19_181142-246x81.png.pagespeed.ic.VjHBEOiFn3.jpg

246x81x2016-02-19_181142-246x81.png.pagespeed.ic.VjHBEOiFn3.jpg

385 ms

hinamaturi0_a.png.pagespeed.ce.eSGCD1KpeK.png

hinamaturi0_a.png.pagespeed.ce.eSGCD1KpeK.png

1041 ms

d8c3bea2d484db57d1cad204608a27a5-246x180.png.pagespeed.ce.DlrUge5KAH.png

d8c3bea2d484db57d1cad204608a27a5-246x180.png.pagespeed.ce.DlrUge5KAH.png

743 ms

200x196x8fc481a8ba40576d59b18f38a9bfd1aa.jpg.pagespeed.ic.vLOroX8fnF.jpg

200x196x8fc481a8ba40576d59b18f38a9bfd1aa.jpg.pagespeed.ic.vLOroX8fnF.jpg

767 ms

a22b456f1e2264c16b69ebff07a6dd77-246x200.png.pagespeed.ce.YtJPskrOuv.png

a22b456f1e2264c16b69ebff07a6dd77-246x200.png.pagespeed.ce.YtJPskrOuv.png

708 ms

273c245e84ca678b395a296d7e9bf504-246x200.jpg

273c245e84ca678b395a296d7e9bf504-246x200.jpg

965 ms

7457fec05789135f0a2d4b1ef7b0b91c-246x200.jpg

7457fec05789135f0a2d4b1ef7b0b91c-246x200.jpg

886 ms

midashi-side.png

midashi-side.png

929 ms

icon-folder-midashi.png

icon-folder-midashi.png

958 ms

x2016-03-04_110410-e1457057521468.png.pagespeed.ic.M1ynRL2h8-.jpg

x2016-03-04_110410-e1457057521468.png.pagespeed.ic.M1ynRL2h8-.jpg

1212 ms

icon-btn-search.png.pagespeed.ce.fnX_MMPcNf.png

icon-btn-search.png.pagespeed.ce.fnX_MMPcNf.png

1062 ms

page-top_off.png.pagespeed.ce.f50p6sNODY.png

page-top_off.png.pagespeed.ce.f50p6sNODY.png

1114 ms

2NG33A+6G7I4Y+KF0+15O4MP

2NG33A+6G7I4Y+KF0+15O4MP

335 ms

collect

collect

107 ms

collect

collect

102 ms

icon-search-midashi.png

icon-search-midashi.png

1035 ms

icon-list-arw.png

icon-list-arw.png

1045 ms

0.gif

0.gif

545 ms

2016-03-14_121928.png

2016-03-14_121928.png

1655 ms

SEO Factors

purezento.jp SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

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

purezento.jp

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