Report Summary

  • 85

    Performance

    Renders faster than
    89% of other websites

  • 48

    Accessibility

    Visual factors better than
    that of 20% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

365blog.jp

ふくしまの地域情報No1ポータルブログサイト『365ブログ』

Page Load Speed

13.8 sec in total

First Response

2.1 sec

Resources Loaded

11.2 sec

Page Rendered

507 ms

365blog.jp screenshot

About Website

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

365日、ふくしまの地域情報やグルメ・美容・ファッション・ショッピングを地元ブロガーによる口コミでいち早くキャッチできるふくしまの地域情報情報No1ポータルブログサイト「365ブログ」。

Visit 365blog.jp

Key Findings

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

Performance Metrics

365blog.jp performance score

85

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

83/100

10%

LCP (Largest Contentful Paint)

Value2.8 s

82/100

25%

SI (Speed Index)

Value4.7 s

68/100

10%

TBT (Total Blocking Time)

Value110 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0.091

92/100

15%

TTI (Time to Interactive)

Value6.0 s

65/100

10%

Network Requests Diagram

365blog.jp

2089 ms

base.css

652 ms

box_index.css

653 ms

box_survey.css

457 ms

pgscroll.js

474 ms

Our browser made a total of 137 requests to load all elements on the main page. We found that 74% of them (102 requests) were addressed to the original 365blog.jp, 15% (20 requests) were made to Img01.365blog.jp and 3% (4 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (3.5 sec) belongs to the original domain 365blog.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 98.8 kB (20%)

Content Size

492.0 kB

After Optimization

393.2 kB

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

HTML Optimization

-79%

Potential reduce by 43.1 kB

  • Original 54.2 kB
  • After minification 47.8 kB
  • After compression 11.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. 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 43.1 kB or 79% of the original size.

Image Optimization

-0%

Potential reduce by 369 B

  • Original 350.4 kB
  • After minification 350.1 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. 365 Blog images are well optimized though.

JavaScript Optimization

-43%

Potential reduce by 20.9 kB

  • Original 48.7 kB
  • After minification 47.2 kB
  • After compression 27.8 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 20.9 kB or 43% of the original size.

CSS Optimization

-89%

Potential reduce by 34.5 kB

  • Original 38.6 kB
  • After minification 15.5 kB
  • After compression 4.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. 365blog.jp needs all CSS files to be minified and compressed as it can save up to 34.5 kB or 89% of the original size.

Requests Breakdown

Number of requests can be reduced by 78 (58%)

Requests Now

134

After Optimization

56

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

Accessibility Review

365blog.jp accessibility score

48

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

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

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

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

365blog.jp best practices score

58

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

High

Browser errors were logged to the console

SEO Factors

365blog.jp SEO score

69

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

    UTF-8

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