Tools & Wizards About Us
lirionet.jp screenshot

Report Summary

  • 57

    Performance

    Renders faster than
    73% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

lirionet.jp

LIRIONET[リリオ]

Page Load Speed

5.6 sec in total

First Response

516 ms

Resources Loaded

4.9 sec

Page Rendered

128 ms

lirionet.jp screenshot

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

Key Findings

We analyzed Lirionet.jp page load time and found that the first response time was 516 ms and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

lirionet.jp performance score

57

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value6.9 s

7/100

25%

SI (Speed Index)

Value8.2 s

20/100

10%

TBT (Total Blocking Time)

Value10 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.09

92/100

15%

TTI (Time to Interactive)

Value5.0 s

76/100

10%

Network Requests Diagram

lirionet.jp

516 ms

lirionet.jp

875 ms

flexslider.css

171 ms

style.css

360 ms

superfish.css

491 ms

Our browser made a total of 92 requests to load all elements on the main page. We found that 70% of them (64 requests) were addressed to the original Lirionet.jp, 26% (24 requests) were made to Lirio.verse.jp and 2% (2 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain Lirionet.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 75.9 kB (7%)

Content Size

1.1 MB

After Optimization

1.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-82%

Potential reduce by 14.6 kB

  • Original 17.7 kB
  • After minification 16.0 kB
  • After compression 3.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. 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 14.6 kB or 82% of the original size.

Image Optimization

-1%

Potential reduce by 8.5 kB

  • Original 977.6 kB
  • After minification 969.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. LIRIONET images are well optimized though.

JavaScript Optimization

-37%

Potential reduce by 33.4 kB

  • Original 91.0 kB
  • After minification 73.4 kB
  • After compression 57.6 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 33.4 kB or 37% of the original size.

CSS Optimization

-79%

Potential reduce by 19.5 kB

  • Original 24.6 kB
  • After minification 20.6 kB
  • After compression 5.1 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 19.5 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 21 (39%)

Requests Now

54

After Optimization

33

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 54 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 10 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

lirionet.jp

lirionet.jp

516 ms

lirionet.jp

lirionet.jp

875 ms

flexslider.css

flexslider.css

171 ms

style.css

style.css

360 ms

superfish.css

superfish.css

491 ms

jquery.min.js

jquery.min.js

17 ms

jquery.flexslider.js

jquery.flexslider.js

665 ms

hoverIntent.js

hoverIntent.js

508 ms

superfish.js

superfish.js

527 ms

supersubs.js

supersubs.js

531 ms

randomdisplay.js

randomdisplay.js

530 ms

setup.js

setup.js

653 ms

00_menu.js

00_menu.js

679 ms

02_topmenu.js

02_topmenu.js

696 ms

jsRSS.cgi

jsRSS.cgi

189 ms

jsRSS.cgi

jsRSS.cgi

189 ms

jsRSS.cgi

jsRSS.cgi

189 ms

jsRSS.cgi

jsRSS.cgi

189 ms

jsRSS.cgi

jsRSS.cgi

189 ms

jsRSS.cgi

jsRSS.cgi

189 ms

jsRSS.cgi

jsRSS.cgi

189 ms

jsRSS.cgi

jsRSS.cgi

188 ms

jsRSS.cgi

jsRSS.cgi

188 ms

jsRSS.cgi

jsRSS.cgi

189 ms

jsRSS.cgi

jsRSS.cgi

189 ms

jsRSS.cgi

jsRSS.cgi

188 ms

jsRSS.cgi

jsRSS.cgi

188 ms

jsRSS.cgi

jsRSS.cgi

188 ms

jsRSS.cgi

jsRSS.cgi

188 ms

jsRSS.cgi

jsRSS.cgi

188 ms

jsRSS.cgi

jsRSS.cgi

188 ms

jsRSS.cgi

jsRSS.cgi

188 ms

jsRSS.cgi

jsRSS.cgi

188 ms

jsRSS.cgi

jsRSS.cgi

188 ms

jsRSS.cgi

jsRSS.cgi

188 ms

jsRSS.cgi

jsRSS.cgi

188 ms

jsRSS.cgi

jsRSS.cgi

187 ms

jsRSS.cgi

jsRSS.cgi

187 ms

nv_gran.png

nv_gran.png

569 ms

lirio.gif

lirio.gif

172 ms

top.jpg

top.jpg

1869 ms

liriomhd_02.png

liriomhd_02.png

218 ms

profile.jpg

profile.jpg

204 ms

profile.jpg

profile.jpg

387 ms

profile.jpg

profile.jpg

418 ms

profile.jpg

profile.jpg

356 ms

profile.jpg

profile.jpg

383 ms

profile.jpg

profile.jpg

614 ms

profile.jpg

profile.jpg

568 ms

profile.jpg

profile.jpg

591 ms

profile.jpg

profile.jpg

610 ms

profile.jpg

profile.jpg

640 ms

profile.jpg

profile.jpg

752 ms

profile.jpg

profile.jpg

775 ms

profile.jpg

profile.jpg

796 ms

profile.jpg

profile.jpg

817 ms

profile.jpg

profile.jpg

829 ms

profile.jpg

profile.jpg

930 ms

liriomhd_03.png

liriomhd_03.png

939 ms

profile.jpg

profile.jpg

970 ms

profile.jpg

profile.jpg

1007 ms

profile.jpg

profile.jpg

1024 ms

profile.jpg

profile.jpg

1115 ms

profile.jpg

profile.jpg

1120 ms

profile.jpg

profile.jpg

1140 ms

profile.jpg

profile.jpg

1204 ms

profile.jpg

profile.jpg

1217 ms

arrow-down.png

arrow-down.png

679 ms

opabkg.png

opabkg.png

684 ms

liriom_03s.png

liriom_03s.png

208 ms

liriom_05s.png

liriom_05s.png

377 ms

liriom_07s.png

liriom_07s.png

378 ms

liriom_03.png

liriom_03.png

1691 ms

liriom_05.png

liriom_05.png

2680 ms

liriom_07.png

liriom_07.png

2682 ms

liriomn01.gif

liriomn01.gif

375 ms

dotted.gif

dotted.gif

517 ms

ga.js

ga.js

16 ms

arrows-000.png

arrows-000.png

1187 ms

__utm.gif

__utm.gif

12 ms

liriom_03s.png

liriom_03s.png

1065 ms

liriom_05s.png

liriom_05s.png

917 ms

liriom_07s.png

liriom_07s.png

988 ms

liriomn01.gif

liriomn01.gif

989 ms

nv_gran.png

nv_gran.png

1467 ms

arrow-down.png

arrow-down.png

1352 ms

opabkg.png

opabkg.png

1355 ms

liriom_03.png

liriom_03.png

481 ms

lirionet.jp

lirionet.jp

170 ms

lirionet.jp

lirionet.jp

342 ms

liriom_05.png

liriom_05.png

172 ms

liriom_07.png

liriom_07.png

165 ms

Accessibility Review

lirionet.jp accessibility score

100

Accessibility Issues

Best Practices

lirionet.jp best practices score

50

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

lirionet.jp SEO score

83

Search Engine Optimization Advices

Mobile Friendly

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/).

Impact

Issue

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: