Report Summary

  • 45

    Performance

    Renders faster than
    64% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 92% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

skyscanner.jp

Skyscanner

Page Load Speed

4.3 sec in total

First Response

492 ms

Resources Loaded

3.6 sec

Page Rendered

182 ms

skyscanner.jp screenshot

About Website

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

世界のレンタカーやホテルだけでなく、多数の格安航空券を無料で比較できます。スカイスキャナーは航空券・旅行の検索サイトです。

Visit skyscanner.jp

Key Findings

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

Performance Metrics

skyscanner.jp performance score

45

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

60/100

10%

LCP (Largest Contentful Paint)

Value2.9 s

80/100

25%

SI (Speed Index)

Value7.5 s

26/100

10%

TBT (Total Blocking Time)

Value2,550 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.117

85/100

15%

TTI (Time to Interactive)

Value11.1 s

20/100

10%

Network Requests Diagram

www.skyscanner.jp

492 ms

core.7e13d7e9.css

27 ms

home_root.css

21 ms

jp67.js

344 ms

common_ja-jp.2f1aa7ca.js

56 ms

Our browser made a total of 80 requests to load all elements on the main page. We found that 8% of them (6 requests) were addressed to the original Skyscanner.jp, 14% (11 requests) were made to Css.skyscnr.com and 6% (5 requests) were made to Api.mixpanel.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Skyscanner.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.4 MB (66%)

Content Size

2.1 MB

After Optimization

715.3 kB

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

HTML Optimization

-75%

Potential reduce by 60.2 kB

  • Original 79.8 kB
  • After minification 72.5 kB
  • After compression 19.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. 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 60.2 kB or 75% of the original size.

Image Optimization

-3%

Potential reduce by 3.3 kB

  • Original 120.0 kB
  • After minification 116.7 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. Skyscanner images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 1.1 MB

  • Original 1.6 MB
  • After minification 1.6 MB
  • After compression 515.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 1.1 MB or 68% of the original size.

CSS Optimization

-75%

Potential reduce by 193.2 kB

  • Original 256.9 kB
  • After minification 256.7 kB
  • After compression 63.7 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. Skyscanner.jp needs all CSS files to be minified and compressed as it can save up to 193.2 kB or 75% of the original size.

Requests Breakdown

Number of requests can be reduced by 46 (62%)

Requests Now

74

After Optimization

28

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

Accessibility Review

skyscanner.jp accessibility score

97

Accessibility Issues

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.

Best Practices

skyscanner.jp best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

skyscanner.jp SEO score

85

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

robots.txt is not valid

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

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Skyscanner.jp can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Japanese. Our system also found out that Skyscanner.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

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