Access blog.goo.ne.jp. gooブログ（goo blog）

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

20/100

10%

LCP (Largest Contentful Paint)

Value6.2 s

11/100

25%

SI (Speed Index)

Value9.7 s

11/100

10%

TBT (Total Blocking Time)

Value7,520 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.264

46/100

15%

TTI (Time to Interactive)

Value25.7 s

0/100

10%

blog.goo.ne.jp

615 ms

import_portal.css

307 ms

photo_ie6.css

311 ms

fixed.css

312 ms

smarttag-blog-blogtop.js

34 ms

Our browser made a total of 147 requests to load all elements on the main page. We found that 20% of them (29 requests) were addressed to the original Blog.goo.ne.jp, 25% (37 requests) were made to Blogimg.goo.ne.jp and 10% (14 requests) were made to Pbs.twimg.com. The less responsive or slowest element that took the longest time to load (2 sec) relates to the external source Adp-pubd-static.adtdp.com.

Content Size

998.3 kB

After Optimization

705.9 kB

In fact, the total size of Blog.goo.ne.jp main page is 998.3 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. 55% of websites need less resources to load. Images take 582.8 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 38.7 kB

Original 52.6 kB
After minification 50.6 kB
After compression 13.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. 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 38.7 kB or 74% of the original size.

Image Optimization

-1%

Potential reduce by 7.2 kB

Original 582.8 kB
After minification 575.6 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. Blog Goo images are well optimized though.

JavaScript Optimization

-63%

Potential reduce by 167.6 kB

Original 265.8 kB
After minification 259.0 kB
After compression 98.2 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 167.6 kB or 63% of the original size.

CSS Optimization

-81%

Potential reduce by 78.9 kB

Original 97.0 kB
After minification 82.7 kB
After compression 18.2 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. Blog.goo.ne.jp needs all CSS files to be minified and compressed as it can save up to 78.9 kB or 81% of the original size.

Requests Now

144

After Optimization

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

Accessibility Issues

These are opportunities to improve the legibility of your content.

High

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

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.

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

High

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

Search Engine Optimization Advices

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

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

High

Image elements do not have [alt] attributes

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/).

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 Blog.goo.ne.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 Blog.goo.ne.jp 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

blog.goo.ne.jp

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

Report Summary

Performance

Accessibility

Best Practices

SEO

gooブログ（goo blog） | 無料でブログを作成

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

blog.goo.ne.jp

import_portal.css

photo_ie6.css

fixed.css

smarttag-blog-blogtop.js

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

blog.goo.ne.jp

import_portal.css

photo_ie6.css

fixed.css

smarttag-blog-blogtop.js

show_ads.js

1.js

portal_gjquery.js

VLTraceDMD.js

cmm.css

main.css

right.css

left.css

base3.css

cs04.css

portal.css

contents.css

header.css

footer.css

pub.css

blocktype.css

goo.gif

megaphone.gif

icon_osusume_2.gif

nicotown.gif

match_298x100c.jpg

sn_90.gif

robo.gif

i_50s.gif

i_42s.gif

i_ids.gif

info_0621-2.png

new_red.png

d78156c6eedc5d96964101e1c42b37e3.jpg

11bdf763406e43ed8520f24c914f2920.jpg

991feb9be46073fc1363112b3088a1b7.jpg

f1f1d4ead5f7ea6e397d1aa4ae95f2a4.jpg

8bf61b5342be3d87ce5756f3f5e3cc0a.jpg

5251ea5b5b0ee6a8029f10917000816c.jpg

a1e16e6514020d70fb1265918251c913.jpg

fa672212572c35842be4e8eec3474d46.jpg

71763e6efe9f9e340f3ccf082b4f2b20.jpg

login.gif