Access techlypost.com. エイケーの店舗デザインから多くのことを学んだ体験

Report Summary

name

value

score

weighting

FCP (First Contentful Paint)

Value1.2 s

99/100

10%

LCP (Largest Contentful Paint)

Value1.2 s

100/100

25%

SI (Speed Index)

Value2.1 s

99/100

10%

TBT (Total Blocking Time)

Value60 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.112

86/100

15%

TTI (Time to Interactive)

Value3.6 s

91/100

10%

www.techlypost.com

1157 ms

analytics.js

345 ms

style.min.css

847 ms

css

342 ms

style.css

96 ms

Our browser made a total of 73 requests to load all elements on the main page. We found that 21% of them (15 requests) were addressed to the original Techlypost.com, 22% (16 requests) were made to Fonts.gstatic.com and 12% (9 requests) were made to I0.wp.com. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source I2.wp.com.

Content Size

1.3 MB

After Optimization

349.2 kB

In fact, the total size of Techlypost.com main page is 1.3 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. 65% of websites need less resources to load. CSS take 596.6 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 140.0 kB

Original 168.7 kB
After minification 166.4 kB
After compression 28.7 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 140.0 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

Original 46.1 kB
After minification 46.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. Techlypost images are well optimized though.

JavaScript Optimization

-61%

Potential reduce by 274.8 kB

Original 451.8 kB
After minification 451.2 kB
After compression 177.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 274.8 kB or 61% of the original size.

CSS Optimization

-84%

Potential reduce by 499.3 kB

Original 596.6 kB
After minification 584.7 kB
After compression 97.3 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. Techlypost.com needs all CSS files to be minified and compressed as it can save up to 499.3 kB or 84% of the original size.

Requests Now

After Optimization

The browser has sent 55 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Techlypost. 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 6 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 interpretation of your content by users in different locales.

High

<html> element does not have a valid value for its [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

Search Engine Optimization Advices

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

High

Page is blocked from indexing

High

robots.txt is not valid

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

Language and Encoding

Language Detected

JA
Language Claimed

EN
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Techlypost.com can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it does not match the claimed English language. Our system also found out that Techlypost.com 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

techlypost.com

Open Graph data is detected on the main page of Techlypost. 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

エイケーの店舗デザインから多くのことを学んだ体験

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)