Tools & Wizards About Us
evilline.com screenshot

Report Summary

  • 52

    Performance

    Renders faster than
    70% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 89

    SEO

    Google-friendlier than
    67% of websites

evilline.com

EVIL LINE RECORDS

Page Load Speed

6.6 sec in total

First Response

808 ms

Resources Loaded

5.5 sec

Page Rendered

226 ms

evilline.com screenshot

About Website

Welcome to evilline.com homepage info - get ready to check EVIL LINE best content for Japan right away, or after learning these important things about evilline.com

EVIL LINE RECORDS 公式サイト。ドレスコーズ、特撮等が所属し、「美少女戦士セーラームーンCrystal」の音楽製作等を行う、アニメ・実写・音楽のメディアミックス化を主眼に置いた新レーベル

Visit evilline.com

Key Findings

We analyzed Evilline.com page load time and found that the first response time was 808 ms and then it took 5.8 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

evilline.com performance score

52

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

62/100

10%

LCP (Largest Contentful Paint)

Value4.9 s

29/100

25%

SI (Speed Index)

Value6.4 s

40/100

10%

TBT (Total Blocking Time)

Value180 ms

92/100

30%

CLS (Cumulative Layout Shift)

Value1

2/100

15%

TTI (Time to Interactive)

Value5.6 s

69/100

10%

Network Requests Diagram

evilline.com

808 ms

stylesheet.css

306 ms

top.css

512 ms

modernizr-2.5.3.js

621 ms

jquery.min.js

30 ms

Our browser made a total of 68 requests to load all elements on the main page. We found that 94% of them (64 requests) were addressed to the original Evilline.com, 3% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (3 sec) belongs to the original domain Evilline.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 252.7 kB (20%)

Content Size

1.3 MB

After Optimization

1.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Evilline.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. 40% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 34.5 kB

  • Original 39.1 kB
  • After minification 24.5 kB
  • After compression 4.6 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. This page needs HTML code to be minified as it can gain 14.6 kB, which is 37% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 34.5 kB or 88% of the original size.

Image Optimization

-11%

Potential reduce by 121.9 kB

  • Original 1.1 MB
  • After minification 985.5 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. Obviously, EVIL LINE needs image optimization as it can save up to 121.9 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-66%

Potential reduce by 75.4 kB

  • Original 114.4 kB
  • After minification 74.0 kB
  • After compression 39.0 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 75.4 kB or 66% of the original size.

CSS Optimization

-85%

Potential reduce by 20.8 kB

  • Original 24.4 kB
  • After minification 16.5 kB
  • After compression 3.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. Evilline.com needs all CSS files to be minified and compressed as it can save up to 20.8 kB or 85% of the original size.

Requests Breakdown

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

Requests Now

67

After Optimization

44

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 67 CSS, Javascripts, AJAX and image requests in order to completely render the main page of EVIL LINE. 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

evilline.com

evilline.com

808 ms

stylesheet.css

stylesheet.css

306 ms

top.css

top.css

512 ms

modernizr-2.5.3.js

modernizr-2.5.3.js

621 ms

jquery.min.js

jquery.min.js

30 ms

jquery.easing.min.js

jquery.easing.min.js

10 ms

swfobject.js

swfobject.js

385 ms

swfforcesize.js

swfforcesize.js

384 ms

jquery.backstretch.min.js

jquery.backstretch.min.js

387 ms

jquery.transit.min.js

jquery.transit.min.js

521 ms

getsocialcount.js

getsocialcount.js

676 ms

elr.main.js

elr.main.js

678 ms

analytics.js

analytics.js

47 ms

bg_white.png

bg_white.png

330 ms

bg_grid_w.png

bg_grid_w.png

793 ms

hd_logo_1.png

hd_logo_1.png

479 ms

hd_nav_audition.png

hd_nav_audition.png

627 ms

hd_nav_link.png

hd_nav_link.png

609 ms

hd_nav_audition_sp.png

hd_nav_audition_sp.png

616 ms

hd_nav_link_sp.png

hd_nav_link_sp.png

723 ms

hd_img_copyright.png

hd_img_copyright.png

871 ms

hd_sns_tw.png

hd_sns_tw.png

899 ms

hd_sns_fb.png

hd_sns_fb.png

905 ms

tri_mcz_def.png

tri_mcz_def.png

1060 ms

arw_white_down.png

arw_white_down.png

1063 ms

tri_mcz_on.png

tri_mcz_on.png

1398 ms

btn_enter.png

btn_enter.png

1210 ms

btn_site.png

btn_site.png

1201 ms

tri_dresscodes_def.png

tri_dresscodes_def.png

1259 ms

arw_white_up.png

arw_white_up.png

1352 ms

tri_dresscodes_on.png

tri_dresscodes_on.png

1674 ms

tri_tokusatsu_def.png

tri_tokusatsu_def.png

1541 ms

tri_tokusatsu_on.png

tri_tokusatsu_on.png

1926 ms

tri_teddyloid_def.png

tri_teddyloid_def.png

1612 ms

tri_teddyloid_on.png

tri_teddyloid_on.png

1804 ms

btn_special.png

btn_special.png

1754 ms

tri_smc_def.png

tri_smc_def.png

2052 ms

arw_black_up.png

arw_black_up.png

1953 ms

tri_smc_on.png

tri_smc_on.png

2570 ms

btn_enter_b.png

btn_enter_b.png

2114 ms

btn_site_b.png

btn_site_b.png

2107 ms

tri_trr_def.png

tri_trr_def.png

2243 ms

tri_trr_on.png

tri_trr_on.png

2504 ms

tri_rockajaponica_def.png

tri_rockajaponica_def.png

2365 ms

evilline-roman-webfont.woff

evilline-roman-webfont.woff

2384 ms

collect

collect

23 ms

tri_rockajaponica_on.png

tri_rockajaponica_on.png

2667 ms

tri_aice5_def.png

tri_aice5_def.png

2305 ms

tri_aice5_on.png

tri_aice5_on.png

2657 ms

tri_smm2_def.png

tri_smm2_def.png

2552 ms

arw_black_down.png

arw_black_down.png

2499 ms

tri_smm2_on.png

tri_smm2_on.png

2718 ms

tri_soregaseiyu_def.png

tri_soregaseiyu_def.png

2610 ms

tri_soregaseiyu_on.png

tri_soregaseiyu_on.png

2805 ms

tri_earphones_def.png

tri_earphones_def.png

2564 ms

tri_earphones_on.png

tri_earphones_on.png

2842 ms

tri_smm3_def.png

tri_smm3_def.png

2651 ms

tri_smm3_on.png

tri_smm3_on.png

3031 ms

tri_joshiraku_def.png

tri_joshiraku_def.png

2625 ms

tri_joshiraku_on.png

tri_joshiraku_on.png

3001 ms

tri_archive01.png

tri_archive01.png

2665 ms

tri_archive02.png

tri_archive02.png

2721 ms

blank.gif

blank.gif

2630 ms

tri_archive_b.png

tri_archive_b.png

2708 ms

tri_archive_w.png

tri_archive_w.png

2768 ms

hd_sns_tw_sp.png

hd_sns_tw_sp.png

2738 ms

hd_sns_fb_sp.png

hd_sns_fb_sp.png

2828 ms

top_default.jpg

top_default.jpg

2837 ms

Accessibility Review

evilline.com accessibility score

100

Accessibility Issues

Best Practices

evilline.com best practices score

75

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

SEO Factors

evilline.com SEO score

89

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

    EN

  • Language Claimed

    JA

  • Encoding

    UTF-8

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

evilline.com

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