Access blog.ameba.jp. アメーバブログ（アメブロ）｜Amebaで無料ブログを始めよう

Report Summary

About Website

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

アメブロでブログを書こう！ 16000人以上の芸能人・有名人ブログを読めるのはAmebaだけ。子育て・ファッション・ペット・旅行・マンガなどのカテゴリも展開。

Visit blog.ameba.jp

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

20/100

10%

LCP (Largest Contentful Paint)

Value7.1 s

5/100

25%

SI (Speed Index)

Value5.5 s

54/100

10%

TBT (Total Blocking Time)

Value370 ms

71/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value5.9 s

66/100

10%

blog.ameba.jp

312 ms

ameblo.jp

898 ms

ameblo.common.hf.white-1.0.2.css

12 ms

portalMain-1.2.0.css

210 ms

portalLib-1.0.0.css

243 ms

Our browser made a total of 78 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Blog.ameba.jp, 81% (63 requests) were made to Stat100.ameba.jp and 5% (4 requests) were made to Stat.profile.ameba.jp. The less responsive or slowest element that took the longest time to load (898 ms) relates to the external source Ameblo.jp.

Content Size

3.9 MB

After Optimization

3.6 MB

In fact, the total size of Blog.ameba.jp main page is 3.9 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. 70% of websites need less resources to load. Images take 3.6 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 45.5 kB

Original 53.9 kB
After minification 47.4 kB
After compression 8.4 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 6.5 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 45.5 kB or 84% of the original size.

Image Optimization

-3%

Potential reduce by 100.9 kB

Original 3.6 MB
After minification 3.5 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. Blog Ameba images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 155.8 kB

Original 240.5 kB
After minification 240.5 kB
After compression 84.7 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 155.8 kB or 65% of the original size.

CSS Optimization

-76%

Potential reduce by 15.6 kB

Original 20.5 kB
After minification 20.5 kB
After compression 4.9 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.ameba.jp needs all CSS files to be minified and compressed as it can save up to 15.6 kB or 76% of the original size.

Requests Now

After Optimization

The browser has sent 72 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Blog Ameba. 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 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 experience of reading tabular or list data using assistive technology, like a screen reader.

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

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

Search Engine Optimization Advices

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

N/A
Encoding

UTF-8

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

blog.ameba.jp

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

Report Summary

Performance

Accessibility

Best Practices

SEO

アメーバブログ（アメブロ）｜Amebaで無料ブログを始めよう

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)