Tools & Wizards About Us
pocari987.blog.jp screenshot

Report Summary

  • 56

    Performance

    Renders faster than
    73% of other websites

  • 60

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

Page Load Speed

7.8 sec in total

First Response

943 ms

Resources Loaded

5.1 sec

Page Rendered

1.8 sec

pocari987.blog.jp screenshot

About Website

Visit pocari987.blog.jp now to see the best up-to-date Pocari 987 Blog content for Japan and also check out these interesting facts you probably never knew about pocari987.blog.jp

Visit pocari987.blog.jp

Key Findings

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

Performance Metrics

pocari987.blog.jp performance score

56

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

64/100

10%

LCP (Largest Contentful Paint)

Value5.4 s

21/100

25%

SI (Speed Index)

Value4.3 s

76/100

10%

TBT (Total Blocking Time)

Value410 ms

66/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value11.6 s

18/100

10%

Network Requests Diagram

pocari987.blog.jp

943 ms

template.css

370 ms

site.css

327 ms

c2.js

382 ms

smartphone.js

400 ms

Our browser made a total of 82 requests to load all elements on the main page. We found that 9% of them (7 requests) were addressed to the original Pocari987.blog.jp, 20% (16 requests) were made to Parts.blog.livedoor.jp and 13% (11 requests) were made to Livedoor.blogimg.jp. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source Livedoor.blogimg.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 210.9 kB (27%)

Content Size

781.7 kB

After Optimization

570.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-86%

Potential reduce by 128.2 kB

  • Original 149.6 kB
  • After minification 126.2 kB
  • After compression 21.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 23.4 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 128.2 kB or 86% of the original size.

Image Optimization

-3%

Potential reduce by 16.7 kB

  • Original 547.6 kB
  • After minification 530.9 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. Pocari 987 Blog images are well optimized though.

JavaScript Optimization

-75%

Potential reduce by 39.3 kB

  • Original 52.7 kB
  • After minification 45.2 kB
  • After compression 13.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 39.3 kB or 75% of the original size.

CSS Optimization

-84%

Potential reduce by 26.8 kB

  • Original 31.8 kB
  • After minification 23.0 kB
  • After compression 5.0 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. Pocari987.blog.jp needs all CSS files to be minified and compressed as it can save up to 26.8 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 30 (37%)

Requests Now

81

After Optimization

51

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

pocari987.blog.jp

pocari987.blog.jp

943 ms

template.css

template.css

370 ms

site.css

site.css

327 ms

c2.js

c2.js

382 ms

smartphone.js

smartphone.js

400 ms

header.js

header.js

586 ms

ad.js

ad.js

404 ms

widgets.js

widgets.js

5 ms

13.js

13.js

340 ms

plugins.css

plugins.css

198 ms

recent_comments.js

recent_comments.js

201 ms

bp.php

bp.php

381 ms

ldblog_calendar_plugin.js

ldblog_calendar_plugin.js

264 ms

ldblog_rss_plugin.js

ldblog_rss_plugin.js

386 ms

bicycle_120x60-02.png

bicycle_120x60-02.png

615 ms

56242e41-s.jpg

56242e41-s.jpg

1151 ms

tatsu05211152_60.gif

tatsu05211152_60.gif

329 ms

ico_f1_s.gif

ico_f1_s.gif

416 ms

banner.blog.with2.net

banner.blog.with2.net

813 ms

56242e41-s.jpg

56242e41-s.jpg

332 ms

keirin88_31.gif

keirin88_31.gif

570 ms

e4d219e5-s.jpg

e4d219e5-s.jpg

361 ms

1fc32888-s.jpg

1fc32888-s.jpg

378 ms

a631259c.jpg

a631259c.jpg

381 ms

514fb1a6-s.jpg

514fb1a6-s.jpg

569 ms

e87e9ce8-s.jpg

e87e9ce8-s.jpg

581 ms

e52779d3-s.jpg

e52779d3-s.jpg

544 ms

482887da-s.jpg

482887da-s.jpg

558 ms

da35d68c-s.jpg

da35d68c-s.jpg

566 ms

bicycle_468x60.png

bicycle_468x60.png

808 ms

big_logo_purchase_blue.gif

big_logo_purchase_blue.gif

318 ms

e4d219e5-s.jpg

e4d219e5-s.jpg

1000 ms

1fc32888-s.jpg

1fc32888-s.jpg

1404 ms

a631259c.jpg

a631259c.jpg

713 ms

514fb1a6-s.jpg

514fb1a6-s.jpg

1160 ms

43918f3a-s.jpg

43918f3a-s.jpg

1798 ms

e87e9ce8-s.jpg

e87e9ce8-s.jpg

1458 ms

e52779d3-s.jpg

e52779d3-s.jpg

1321 ms

482887da-s.jpg

482887da-s.jpg

1462 ms

da35d68c-s.jpg

da35d68c-s.jpg

1516 ms

fbb7d2f7-s.jpg

fbb7d2f7-s.jpg

1639 ms

body_back.jpg

body_back.jpg

740 ms

logo_blog_premium.png

logo_blog_premium.png

357 ms

c

c

360 ms

logo_livedoor.gif

logo_livedoor.gif

210 ms

logo_blog.gif

logo_blog.gif

212 ms

entry_icon.png

entry_icon.png

200 ms

calendar_icon.png

calendar_icon.png

312 ms

article-title_back.gif

article-title_back.gif

318 ms

sidetitle_back.jpg

sidetitle_back.jpg

315 ms

plugin-13.gif

plugin-13.gif

674 ms

jsonloader.js

jsonloader.js

310 ms

like.php

like.php

146 ms

like.php

like.php

127 ms

like.php

like.php

145 ms

like.php

like.php

158 ms

like.php

like.php

152 ms

like.php

like.php

142 ms

like.php

like.php

170 ms

like.php

like.php

161 ms

like.php

like.php

161 ms

like.php

like.php

169 ms

qeKvIRsJabD.js

qeKvIRsJabD.js

503 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

564 ms

c

c

343 ms

c

c

355 ms

c

c

358 ms

popular_articles.json

popular_articles.json

513 ms

recent_comments.json

recent_comments.json

367 ms

2016-03.json

2016-03.json

381 ms

u.js

u.js

334 ms

button.0308b81ff1714e446f674b5b9793f2cd.js

button.0308b81ff1714e446f674b5b9793f2cd.js

22 ms

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html

52 ms

feed

feed

330 ms

jot.html

jot.html

3 ms

cast

cast

371 ms

ajs.php

ajs.php

340 ms

ad.js

ad.js

183 ms

lg.php

lg.php

164 ms

pcad.js

pcad.js

184 ms

rakuten_widget.js

rakuten_widget.js

913 ms

mtwidget04.affiliate.rakuten.co.jp

mtwidget04.affiliate.rakuten.co.jp

297 ms

Accessibility Review

pocari987.blog.jp accessibility score

60

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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.

Best Practices

pocari987.blog.jp best practices score

67

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

pocari987.blog.jp SEO score

83

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

    UTF-8

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

pocari987.blog.jp

Open Graph data is detected on the main page of Pocari 987 Blog. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: