Tools & Wizards About Us
iflyer.tv screenshot

Report Summary

  • 44

    Performance

    Renders faster than
    63% of other websites

  • 45

    Accessibility

    Visual factors better than
    that of 19% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

iflyer.tv

iFLYER: ミュージックイベント・ライブイベント・クラブイベント情報

Page Load Speed

1.9 sec in total

First Response

11 ms

Resources Loaded

1.5 sec

Page Rendered

388 ms

iflyer.tv screenshot

About Website

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

オフィシャルライブハウスやクラブイベント、アーティストイベントを入手しよう。iFLYER.tvでは常に日本中の最新のイベント情報を配信しています。パソコンや携帯電話からこまめにチェックしてディスカウント情報活用してナイトライフをエンジョイしよう！

Visit iflyer.tv

Key Findings

We analyzed Iflyer.tv page load time and found that the first response time was 11 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

iflyer.tv performance score

44

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

56/100

10%

LCP (Largest Contentful Paint)

Value5.0 s

26/100

25%

SI (Speed Index)

Value4.3 s

76/100

10%

TBT (Total Blocking Time)

Value1,290 ms

18/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value8.0 s

43/100

10%

Network Requests Diagram

iflyer.tv

11 ms

iflyer.tv

789 ms

js

155 ms

srvrsts.php

718 ms

style.css

55 ms

Our browser made a total of 18 requests to load all elements on the main page. We found that 28% of them (5 requests) were addressed to the original Iflyer.tv, 11% (2 requests) were made to Googletagmanager.com and 11% (2 requests) were made to D10s23uwhf0dgz.cloudfront.net. The less responsive or slowest element that took the longest time to load (789 ms) belongs to the original domain Iflyer.tv.

Page Optimization Overview & Recommendations

Page size can be reduced by 97.9 kB (57%)

Content Size

172.0 kB

After Optimization

74.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Iflyer.tv main page is 172.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. 40% of websites need less resources to load. Javascripts take 86.4 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 65.8 kB

  • Original 80.7 kB
  • After minification 74.0 kB
  • After compression 14.9 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 65.8 kB or 82% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 4.0 kB
  • After minification 4.0 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. IFLYER images are well optimized though.

JavaScript Optimization

-37%

Potential reduce by 32.0 kB

  • Original 86.4 kB
  • After minification 86.4 kB
  • After compression 54.4 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 32.0 kB or 37% of the original size.

CSS Optimization

-15%

Potential reduce by 125 B

  • Original 862 B
  • After minification 862 B
  • After compression 737 B

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. Iflyer.tv needs all CSS files to be minified and compressed as it can save up to 125 B or 15% of the original size.

Requests Breakdown

Number of requests can be reduced by 4 (31%)

Requests Now

13

After Optimization

9

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

iflyer.tv

iflyer.tv

11 ms

iflyer.tv

iflyer.tv

789 ms

js

js

155 ms

srvrsts.php

srvrsts.php

718 ms

style.css

style.css

55 ms

global.css.php

global.css.php

53 ms

jquery.min.js

jquery.min.js

49 ms

global.js.php

global.js.php

70 ms

css

css

145 ms

fbevents.js

fbevents.js

102 ms

blank.gif

blank.gif

99 ms

ja.png

ja.png

215 ms

iflyer-icons.ttf

iflyer-icons.ttf

76 ms

js

js

39 ms

analytics.js

analytics.js

89 ms

collect

collect

14 ms

collect

collect

13 ms

ga-audiences

ga-audiences

81 ms

Accessibility Review

iflyer.tv accessibility score

45

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

[role] values are not valid

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.

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a valid value for its [lang] attribute.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

iflyer.tv best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

iflyer.tv SEO score

82

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

High

Document doesn't have a valid hreflang

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Iflyer.tv 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 Iflyer.tv 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

iflyer.tv

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