Access 365blog.jp. ふくしまの地域情報Ｎｏ１ポータルブログサイト『365ブログ』

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

68/100

10%

LCP (Largest Contentful Paint)

Value3.7 s

56/100

25%

SI (Speed Index)

Value4.2 s

78/100

10%

TBT (Total Blocking Time)

Value110 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0.085

93/100

15%

TTI (Time to Interactive)

Value5.4 s

72/100

10%

365blog.jp

1005 ms

base.css

501 ms

box_index.css

503 ms

box_survey.css

342 ms

pgscroll.js

343 ms

Our browser made a total of 123 requests to load all elements on the main page. We found that 79% of them (97 requests) were addressed to the original 365blog.jp, 15% (18 requests) were made to Img01.365blog.jp and 2% (2 requests) were made to Admin.365blog.jp. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Img01.365blog.jp.

Content Size

478.2 kB

After Optimization

397.9 kB

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

HTML Optimization

-79%

Potential reduce by 39.0 kB

Original 49.3 kB
After minification 43.1 kB
After compression 10.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. This page needs HTML code to be minified as it can gain 6.2 kB, which is 13% 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 39.0 kB or 79% of the original size.

Image Optimization

-1%

Potential reduce by 4.7 kB

Original 351.7 kB
After minification 347.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

-6%

Potential reduce by 2.2 kB

Original 38.6 kB
After minification 38.1 kB
After compression 36.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. This website has mostly compressed JavaScripts.

CSS Optimization

-89%

Potential reduce by 34.4 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.4 kB or 89% of the original size.

Requests Now

120

After Optimization

The browser has sent 120 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 4 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 keyboard navigation in your application.

High

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

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

High

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

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

High

Browser errors were logged to the console

Search Engine Optimization Advices

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

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

365blog.jp

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:

Report Summary

Performance

Accessibility

Best Practices

SEO

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

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

365blog.jp

base.css

box_index.css

box_survey.css

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

365blog.jp

base.css

box_index.css

box_survey.css

pgscroll.js

hide.js

jsapi

loader.js

20240420_1-s.gif

240501-1_gQt-s.jpg

i-img600x450-1705828697mjpjqa7-s.jpg

qr.php

20240505_112750-s.jpg

IMG_2060_1-s.JPG

11138588_349775288553224_4712531580976456760_n_6-s.png

waxhsealhstampssk10k-s.jpeg

waxhsealhstampssk13k-s.jpeg

20240404_071804-s.jpg

20240403_1205042655001989-s.jpg

PhotoCollage_1691630461987-s.jpg

image02178661560-s.jpeg

rakuraku-kisyouyohoushi-s.jpg

IMG_3105-s.jpg

sp-022490000s1664318560-s.jpg

niconico-s.gif

20220703-G1_1-s.jpg

sp-064181100s1656152045-s.jpg

IMG_2745-s.jpg

77A0CA34-29CF-4AAE-9BB8-B14039A12CA8-s.jpeg

bg_body.gif

bg_body2.gif

bg_head.gif

blog_logo.gif

btn_pwmenu.gif

btn_login.gif

top1.gif

top4.gif

top5.gif

bg_title_center.gif

ico_cursor.gif

ico_point.gif

ico_rss.gif

bg_dot.gif