Access lirionet.jp. LIRIONET[リリオ]

Report Summary

About Website

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

アスリートやデザイナーが発信する総合情報サイト！インタビューや対談も随時配信中。

Visit lirionet.jp

name

value

score

weighting

FCP (First Contentful Paint)

Value5.3 s

7/100

10%

LCP (Largest Contentful Paint)

Value8.2 s

2/100

25%

SI (Speed Index)

Value9.2 s

13/100

10%

TBT (Total Blocking Time)

Value70 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.161

73/100

15%

TTI (Time to Interactive)

Value6.1 s

63/100

10%

lirionet.jp

702 ms

flexslider.css

315 ms

style.css

469 ms

superfish.css

355 ms

jquery-1.6.2.min.js

906 ms

Our browser made a total of 104 requests to load all elements on the main page. We found that 66% of them (69 requests) were addressed to the original Lirionet.jp, 31% (32 requests) were made to Lirio.verse.jp and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3 sec) belongs to the original domain Lirionet.jp.

Content Size

2.6 MB

After Optimization

2.4 MB

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

HTML Optimization

-81%

Potential reduce by 20.0 kB

Original 24.8 kB
After minification 23.1 kB
After compression 4.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 20.0 kB or 81% of the original size.

Image Optimization

-2%

Potential reduce by 55.7 kB

Original 2.4 MB
After minification 2.3 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. LIRIONET images are well optimized though.

JavaScript Optimization

-62%

Potential reduce by 94.5 kB

Original 151.3 kB
After minification 133.4 kB
After compression 56.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 94.5 kB or 62% of the original size.

CSS Optimization

-77%

Potential reduce by 32.7 kB

Original 42.6 kB
After minification 39.6 kB
After compression 9.9 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. Lirionet.jp needs all CSS files to be minified and compressed as it can save up to 32.7 kB or 77% of the original size.

Requests Now

101

After Optimization

The browser has sent 101 CSS, Javascripts, AJAX and image requests in order to completely render the main page of LIRIONET. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and as a result speed up the page load time.

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

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

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 doesn't use 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 Lirionet.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 Lirionet.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

lirionet.jp

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

LIRIONET[リリオ]

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)