Report Summary

  • 38

    Performance

    Renders faster than
    57% of other websites

  • 57

    Accessibility

    Visual factors better than
    that of 34% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    29% of websites

  • 64

    SEO

    Google-friendlier than
    34% of websites

asablo.jp

アサブロ ~ ASAHIネットのブログサービス

Page Load Speed

7.6 sec in total

First Response

998 ms

Resources Loaded

6.5 sec

Page Rendered

134 ms

asablo.jp screenshot

About Website

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

Visit asablo.jp

Key Findings

We analyzed Asablo.jp page load time and found that the first response time was 998 ms and then it took 6.6 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

asablo.jp performance score

38

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value6.7 s

7/100

25%

SI (Speed Index)

Value7.1 s

31/100

10%

TBT (Total Blocking Time)

Value650 ms

46/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value9.9 s

27/100

10%

Network Requests Diagram

asablo.jp

998 ms

www.asablo.jp

520 ms

1113 ms

dir.css

526 ms

media-dir.css

531 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 5% of them (2 requests) were addressed to the original Asablo.jp, 48% (20 requests) were made to Asahi-net.jp and 14% (6 requests) were made to S.asablo.jp. The less responsive or slowest element that took the longest time to load (3.1 sec) relates to the external source Dir.asablo.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 84.0 kB (29%)

Content Size

292.0 kB

After Optimization

208.0 kB

In fact, the total size of Asablo.jp main page is 292.0 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. Images take 159.1 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 14.3 kB

  • Original 18.6 kB
  • After minification 17.4 kB
  • After compression 4.2 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 14.3 kB or 77% of the original size.

Image Optimization

-7%

Potential reduce by 11.1 kB

  • Original 159.1 kB
  • After minification 148.0 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. Asablo images are well optimized though.

JavaScript Optimization

-47%

Potential reduce by 46.9 kB

  • Original 99.9 kB
  • After minification 97.6 kB
  • After compression 53.0 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 46.9 kB or 47% of the original size.

CSS Optimization

-80%

Potential reduce by 11.6 kB

  • Original 14.4 kB
  • After minification 10.8 kB
  • After compression 2.8 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. Asablo.jp needs all CSS files to be minified and compressed as it can save up to 11.6 kB or 80% of the original size.

Requests Breakdown

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

Requests Now

37

After Optimization

25

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

Accessibility Review

asablo.jp accessibility score

57

Accessibility Issues

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

asablo.jp best practices score

58

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

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

asablo.jp SEO score

64

Search Engine Optimization Advices

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

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Asablo.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 Asablo.jp main page’s claimed encoding is shift_jis. 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

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