Report Summary

  • 18

    Performance

    Renders faster than
    38% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 57% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    47% of websites

  • 100

    SEO

    Google-friendlier than
    96% of websites

ameba.jp

Ameba (アメーバ)|ブログ&ゲーム 1万人以上の芸能人ブログや定番アメーバピグで遊ぼう♪

Page Load Speed

1.8 sec in total

First Response

333 ms

Resources Loaded

1.4 sec

Page Rendered

0 ms

ameba.jp screenshot

About Website

Welcome to ameba.jp homepage info - get ready to check Ameba best content for Japan right away, or after learning these important things about ameba.jp

人気アーティストやアイドル、スポーツ選手など17,000人以上の芸能人・有名人ブログを読めるのはAmebaだけ。Amebaに無料登録して、ブログを書いたりピグで遊んでみよう!

Visit ameba.jp

Key Findings

We analyzed Ameba.jp page load time and found that the first response time was 333 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

ameba.jp performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

19/100

10%

LCP (Largest Contentful Paint)

Value10.5 s

0/100

25%

SI (Speed Index)

Value11.2 s

5/100

10%

TBT (Total Blocking Time)

Value4,630 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value20.4 s

2/100

10%

Network Requests Diagram

ameba.jp

333 ms

www.ameba.jp

471 ms

common.1.000.css

203 ms

footer_www.1.000.css

486 ms

login.1.001.css

218 ms

Our browser made a total of 16 requests to load all elements on the main page. We found that 13% of them (2 requests) were addressed to the original Ameba.jp, 81% (13 requests) were made to Stat100.ameba.jp and 6% (1 request) were made to Ot.ca-mpr.jp. The less responsive or slowest element that took the longest time to load (770 ms) relates to the external source Stat100.ameba.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 107.5 kB (70%)

Content Size

154.5 kB

After Optimization

47.0 kB

In fact, the total size of Ameba.jp main page is 154.5 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. 15% of websites need less resources to load. Javascripts take 128.8 kB which makes up the majority of the site volume.

HTML Optimization

-62%

Potential reduce by 2.1 kB

  • Original 3.5 kB
  • After minification 3.5 kB
  • After compression 1.3 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 2.1 kB or 62% of the original size.

JavaScript Optimization

-69%

Potential reduce by 88.4 kB

  • Original 128.8 kB
  • After minification 117.7 kB
  • After compression 40.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 88.4 kB or 69% of the original size.

CSS Optimization

-77%

Potential reduce by 17.0 kB

  • Original 22.2 kB
  • After minification 19.4 kB
  • After compression 5.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. Ameba.jp needs all CSS files to be minified and compressed as it can save up to 17.0 kB or 77% of the original size.

Requests Breakdown

Number of requests can be reduced by 12 (86%)

Requests Now

14

After Optimization

2

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

Accessibility Review

ameba.jp accessibility score

79

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[role]s are not contained by their required parent element

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

Buttons do not have an accessible name

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.

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

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

Best Practices

ameba.jp best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

ameba.jp SEO score

100

Search Engine Optimization Advices

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

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 Ameba.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 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

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