Access kyo2.jp. 「京つう」はみんなで作る京都ブログマガジンです

name

value

score

weighting

FCP (First Contentful Paint)

Value4.9 s

10/100

10%

LCP (Largest Contentful Paint)

Value11.4 s

0/100

25%

SI (Speed Index)

Value9.2 s

13/100

10%

TBT (Total Blocking Time)

Value230 ms

87/100

30%

CLS (Cumulative Layout Shift)

Value0.149

76/100

15%

TTI (Time to Interactive)

Value9.6 s

29/100

10%

kyo2.jp

504 ms

www.kyo2.jp

1298 ms

js

69 ms

new_base.css

479 ms

new_box_index.css

653 ms

Our browser made a total of 134 requests to load all elements on the main page. We found that 57% of them (77 requests) were addressed to the original Kyo2.jp, 20% (27 requests) were made to Img01.kyo2.jp and 5% (7 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Img01.kyo2.jp.

Content Size

1.6 MB

After Optimization

1.4 MB

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

HTML Optimization

-80%

Potential reduce by 82.1 kB

Original 102.2 kB
After minification 78.8 kB
After compression 20.1 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 23.4 kB, which is 23% 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 82.1 kB or 80% of the original size.

Image Optimization

-3%

Potential reduce by 30.3 kB

Original 1.2 MB
After minification 1.1 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. Kyo 2 images are well optimized though.

JavaScript Optimization

-13%

Potential reduce by 36.7 kB

Original 282.9 kB
After minification 268.8 kB
After compression 246.2 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 36.7 kB or 13% of the original size.

CSS Optimization

-79%

Potential reduce by 55.1 kB

Original 70.1 kB
After minification 39.8 kB
After compression 15.0 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. Kyo2.jp needs all CSS files to be minified and compressed as it can save up to 55.1 kB or 79% of the original size.

Requests Now

129

After Optimization

The browser has sent 129 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Kyo 2. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 7 to 1 for CSS 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

Heading elements are not in a sequentially-descending order

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 items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

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

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

Search Engine Optimization Advices

To appear in search results, crawlers need access to your app.

High

Page is blocked from indexing

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

High

Image elements do not have [alt] attributes

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

JA
Encoding

UTF-8

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

kyo2.jp

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

「 京つう 」はみんなで作る京都ブログマガジンです

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

kyo2.jp

www.kyo2.jp

js

new_base.css

new_box_index.css

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

kyo2.jp

www.kyo2.jp

js

new_base.css

new_box_index.css

box_survey.css

box_search.css

jquery.min.js

pgscroll.js

hide.js

bse.js

adclick.js

ui.core.js

ui.tabs.js

ui.tabs.css

layzr.js

cse.js

rss_reader.php

rss_reader.php

rss_reader.php

sdk.js

rss_reader.php

rss_reader.php

widgets.js

arealink.js

blocksit.min.js

cse.js

sp-068877200s1714906727-s.jpg

240501-1_gQt-s.jpg

DSC06638-s.JPG

IMG_9078-s.JPEG

P5050408-s.JPG

202013_0-s.jpg

RFT-120MTF-s.jpg

shs-IMG_0326-s.jpg

IMG_8458-s.jpg

LINE_capture_736520632.820146-s.jpeg

sp-027854800s1714815765-s.jpg

sp-053780300s1714653608-s.jpg

IMG_4025-s.JPG

1sk2k-s.jpg

%E5%8F%A4%E6%B0%91%E5%85%B72_2-s.jpeg

240502-s.JPG

「京つう」はみんなで作る京都ブログマガジンです