Tools & Wizards About Us
j-lyric.net screenshot

Report Summary

  • 56

    Performance

    Renders faster than
    74% of other websites

  • 69

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    57% of websites

  • 96

    SEO

    Google-friendlier than
    91% of websites

j-lyric.net

歌詞検索J-Lyric.net

Page Load Speed

3.6 sec in total

First Response

923 ms

Resources Loaded

2.4 sec

Page Rendered

239 ms

j-lyric.net screenshot

About Website

Welcome to j-lyric.net homepage info - get ready to check J Lyric best content for Japan right away, or after learning these important things about j-lyric.net

歌詞検索J-Lyric.netは、無料で歌詞の検索・閲覧ができる歌詞検索サイトです。JPOP、演歌、歌謡曲、アニメ主題歌、ドラマ主題歌、映画主題歌などを簡単な操作で検索することができます。

Visit j-lyric.net

Key Findings

We analyzed J-lyric.net page load time and found that the first response time was 923 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

j-lyric.net performance score

56

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

72/100

10%

LCP (Largest Contentful Paint)

Value2.4 s

92/100

25%

SI (Speed Index)

Value4.5 s

72/100

10%

TBT (Total Blocking Time)

Value2,410 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.079

94/100

15%

TTI (Time to Interactive)

Value10.3 s

25/100

10%

Network Requests Diagram

j-lyric.net

923 ms

index.css

622 ms

plusone.js

101 ms

show_ads.js

8 ms

widgets.js

83 ms

Our browser made a total of 68 requests to load all elements on the main page. We found that 13% of them (9 requests) were addressed to the original J-lyric.net, 37% (25 requests) were made to Ecx.images-amazon.com and 10% (7 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Quantum-life.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 62.1 kB (26%)

Content Size

241.0 kB

After Optimization

178.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of J-lyric.net main page is 241.0 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. Images take 136.4 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 27.9 kB

  • Original 37.5 kB
  • After minification 37.3 kB
  • After compression 9.5 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 27.9 kB or 75% of the original size.

Image Optimization

-1%

Potential reduce by 988 B

  • Original 136.4 kB
  • After minification 135.4 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. J Lyric images are well optimized though.

JavaScript Optimization

-40%

Potential reduce by 20.7 kB

  • Original 52.0 kB
  • After minification 51.9 kB
  • After compression 31.3 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 20.7 kB or 40% of the original size.

CSS Optimization

-82%

Potential reduce by 12.5 kB

  • Original 15.1 kB
  • After minification 11.7 kB
  • After compression 2.6 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. J-lyric.net needs all CSS files to be minified and compressed as it can save up to 12.5 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 22 (34%)

Requests Now

65

After Optimization

43

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

j-lyric.net

j-lyric.net

923 ms

index.css

index.css

622 ms

plusone.js

plusone.js

101 ms

show_ads.js

show_ads.js

8 ms

widgets.js

widgets.js

83 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

67 ms

61OfW9QQJYL._SL160_.jpg

61OfW9QQJYL._SL160_.jpg

65 ms

ybm16.gif

ybm16.gif

650 ms

back2.png

back2.png

193 ms

hatena.gif

hatena.gif

228 ms

google.gif

google.gif

397 ms

favorites.gif

favorites.gif

399 ms

ja_follow_me-a.png

ja_follow_me-a.png

399 ms

jasrac.png

jasrac.png

398 ms

311Mw6DGyUL._SL160_.jpg

311Mw6DGyUL._SL160_.jpg

61 ms

615UpIYortL._SL160_.jpg

615UpIYortL._SL160_.jpg

61 ms

41wkMqtW%2BuL._SL160_.jpg

41wkMqtW%2BuL._SL160_.jpg

61 ms

51z0c3yt1%2BL._SL160_.jpg

51z0c3yt1%2BL._SL160_.jpg

63 ms

51ZTCnEsWNL._SL160_.jpg

51ZTCnEsWNL._SL160_.jpg

62 ms

51fhlU9%2BEGL._SL160_.jpg

51fhlU9%2BEGL._SL160_.jpg

58 ms

41tXcyHsQAL._SL160_.jpg

41tXcyHsQAL._SL160_.jpg

60 ms

31E9iqu2D8L._SL75_.jpg

31E9iqu2D8L._SL75_.jpg

63 ms

51t1IBUZSCL._SL75_.jpg

51t1IBUZSCL._SL75_.jpg

62 ms

41Y0Ys8KvcL._SL75_.jpg

41Y0Ys8KvcL._SL75_.jpg

64 ms

41aM81ecFzL._SL75_.jpg

41aM81ecFzL._SL75_.jpg

63 ms

51HfHb8uTTL._SL75_.jpg

51HfHb8uTTL._SL75_.jpg

65 ms

51QpEpb9QeL._SL75_.jpg

51QpEpb9QeL._SL75_.jpg

64 ms

514OBuBia-L._SL75_.jpg

514OBuBia-L._SL75_.jpg

64 ms

51MPerUPmjL._SL75_.jpg

51MPerUPmjL._SL75_.jpg

65 ms

41Q%2Bp04nZuL._SL75_.jpg

41Q%2Bp04nZuL._SL75_.jpg

65 ms

51%2B8sEwSjiL._SL75_.jpg

51%2B8sEwSjiL._SL75_.jpg

67 ms

51P0%2BXnUazL._SL75_.jpg

51P0%2BXnUazL._SL75_.jpg

65 ms

51EEP-4E3WL._SL75_.jpg

51EEP-4E3WL._SL75_.jpg

65 ms

51QO1yuy2bL._SL75_.jpg

51QO1yuy2bL._SL75_.jpg

66 ms

61mTcJD02eL._SL75_.jpg

61mTcJD02eL._SL75_.jpg

67 ms

51CopsywpjL._SL75_.jpg

51CopsywpjL._SL75_.jpg

66 ms

61lIYRHPBvL._SL75_.jpg

61lIYRHPBvL._SL75_.jpg

66 ms

413K53qiHgL._SL75_.jpg

413K53qiHgL._SL75_.jpg

67 ms

ca-pub-4888448476575673.js

ca-pub-4888448476575673.js

53 ms

zrt_lookup.html

zrt_lookup.html

50 ms

show_ads_impl.js

show_ads_impl.js

53 ms

arrow_1.png

arrow_1.png

259 ms

ads

ads

144 ms

ga.js

ga.js

38 ms

osd.js

osd.js

10 ms

ads

ads

190 ms

ads

ads

187 ms

like.php

like.php

200 ms

ads

ads

125 ms

__utm.gif

__utm.gif

48 ms

index.php

index.php

1123 ms

button.831500944bc3eb7ea5276ccdc3f71d2e.js

button.831500944bc3eb7ea5276ccdc3f71d2e.js

145 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

26 ms

fastbutton

fastbutton

124 ms

ads

ads

118 ms

postmessageRelay

postmessageRelay

65 ms

collect

collect

86 ms

api.js

api.js

50 ms

core:rpc:shindig.random:shindig.sha1.js

core:rpc:shindig.random:shindig.sha1.js

129 ms

2536007149-postmessagerelay.js

2536007149-postmessagerelay.js

68 ms

abg.js

abg.js

72 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

56 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

54 ms

W5F8_SL0XFawnjxHGsZjJA.ttf

W5F8_SL0XFawnjxHGsZjJA.ttf

114 ms

tweet_button.6a78875565a912489e9aef879c881358.ja.html

tweet_button.6a78875565a912489e9aef879c881358.ja.html

69 ms

vpc6VNjRPXV.js

vpc6VNjRPXV.js

172 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

191 ms

jot

jot

97 ms

Accessibility Review

j-lyric.net accessibility score

69

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Names and labels

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.

Impact

Issue

High

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

High

Form elements do not have associated labels

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

Best Practices

j-lyric.net best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

j-lyric.net SEO score

96

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 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 J-lyric.net 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 J-lyric.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

j-lyric.net

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