Access slowcore.net. 【公式】スローコア

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

31/100

10%

LCP (Largest Contentful Paint)

Value31.5 s

0/100

25%

SI (Speed Index)

Value21.1 s

0/100

10%

TBT (Total Blocking Time)

Value2,070 ms

7/100

30%

CLS (Cumulative Layout Shift)

Value0.644

9/100

15%

TTI (Time to Interactive)

Value35.4 s

0/100

10%

slowcore.net

546 ms

slowcore.net

902 ms

reset.css

176 ms

base02.css

354 ms

210708add.css

510 ms

Our browser made a total of 124 requests to load all elements on the main page. We found that 71% of them (88 requests) were addressed to the original Slowcore.net, 5% (6 requests) were made to Cdnjs.cloudflare.com and 4% (5 requests) were made to Form.qualva.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Slowcore.net.

Content Size

984.6 kB

After Optimization

819.6 kB

In fact, the total size of Slowcore.net main page is 984.6 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. 55% of websites need less resources to load. Javascripts take 520.5 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 33.0 kB

Original 45.8 kB
After minification 45.0 kB
After compression 12.8 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 33.0 kB or 72% of the original size.

Image Optimization

-2%

Potential reduce by 8.5 kB

Original 369.2 kB
After minification 360.7 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. Slowcore images are well optimized though.

JavaScript Optimization

-20%

Potential reduce by 104.4 kB

Original 520.5 kB
After minification 520.3 kB
After compression 416.1 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 104.4 kB or 20% of the original size.

CSS Optimization

-39%

Potential reduce by 19.1 kB

Original 49.1 kB
After minification 47.9 kB
After compression 30.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. Slowcore.net needs all CSS files to be minified and compressed as it can save up to 19.1 kB or 39% of the original size.

Requests Now

119

After Optimization

The browser has sent 119 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Slowcore. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 12 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 the experience of reading tabular or list data using assistive technology, like a screen reader.

High

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

High

Definition list items are not wrapped in <dl> elements

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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 interpretation of your content by users in different locales.

High

<html> element does not have a [lang] attribute

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

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

Search Engine Optimization Advices

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

High

Links are not crawlable

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

N/A
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Slowcore.net can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Slowcore.net 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

slowcore.net

Open Graph data is detected on the main page of Slowcore. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook:

Report Summary

Performance

Accessibility

Best Practices

SEO

【公式】スローコア - SlowcoreLife

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

slowcore.net

slowcore.net

reset.css

base02.css

210708add.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

slowcore.net

slowcore.net

reset.css

base02.css

210708add.css

lightbox.css

lightbox.min.css

jquery-1.9.1.min.js

common.js

714jr0ob.js

qtag

jquery-1.12.4.min.js

lightbox.min.js

jQueryAutoHeight.js

css_browser_selector.js

echo.min.js

gtm.js

pc_logo01.webp

pc_btn_order.webp

sp_gnav_order_off.webp

sp_logo01.webp

btn_order.webp

top_index.webp

sp_top_index.webp

S3_attention.webp

S3_sp_attention.webp

btn_link.webp

manzokudo_pc.webp

manzokudo_sp.webp

S1_voice_st_img01.webp

arrow_under01.webp

S1_voice_st_img02.webp

arrow_under02.webp

S1_voice_ko_img01.webp

S1_voice_ji_img02.webp

S10_hikaku.webp

S10_sp_hikaku.webp

S5_h2_title.webp

S5_sp_h2_title.webp

S5_img_media.webp

S5_sp_img_media.webp

S5_img_himitsu.webp

S5_sp_img_himitsu.webp