Tools & Wizards About Us
flyradar.eu screenshot

Report Summary

  • 30

    Performance

    Renders faster than
    50% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

flyradar.eu

FLYRADAR - Flight Tracker Live on Fly Radar 24 - Air Traffic

Page Load Speed

3.2 sec in total

First Response

565 ms

Resources Loaded

2.2 sec

Page Rendered

347 ms

flyradar.eu screenshot

About Website

Click here to check amazing FLYRADAR content. Otherwise, check out these important facts you probably never knew about flyradar.eu

FLYRADAR - See all flight information on fly radar 24. You can follow the flights of most passenger planes and helicopters. Flight tracker live.

Visit flyradar.eu

Key Findings

We analyzed Flyradar.eu page load time and found that the first response time was 565 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

flyradar.eu performance score

30

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.9 s

86/100

10%

LCP (Largest Contentful Paint)

Value5.7 s

17/100

25%

SI (Speed Index)

Value8.0 s

22/100

10%

TBT (Total Blocking Time)

Value6,480 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value21.5 s

1/100

10%

Network Requests Diagram

flyradar.eu

565 ms

style.min.css

185 ms

unsemantic-grid.min.css

308 ms

style.min.css

338 ms

mobile.min.css

352 ms

Our browser made a total of 25 requests to load all elements on the main page. We found that 44% of them (11 requests) were addressed to the original Flyradar.eu, 24% (6 requests) were made to Radarbox.com and 16% (4 requests) were made to Cdn.radarbox.com. The less responsive or slowest element that took the longest time to load (597 ms) relates to the external source Radarbox.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 61.7 kB (23%)

Content Size

264.8 kB

After Optimization

203.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Flyradar.eu main page is 264.8 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. 30% of websites need less resources to load. Images take 165.6 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 35.0 kB

  • Original 49.2 kB
  • After minification 48.7 kB
  • After compression 14.2 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 35.0 kB or 71% of the original size.

Image Optimization

-13%

Potential reduce by 22.1 kB

  • Original 165.6 kB
  • After minification 143.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, FLYRADAR needs image optimization as it can save up to 22.1 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-9%

Potential reduce by 164 B

  • Original 1.8 kB
  • After minification 1.8 kB
  • After compression 1.7 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. This website has mostly compressed JavaScripts.

CSS Optimization

-9%

Potential reduce by 4.4 kB

  • Original 48.2 kB
  • After minification 48.2 kB
  • After compression 43.8 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. Flyradar.eu has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 10 (43%)

Requests Now

23

After Optimization

13

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

flyradar.eu

flyradar.eu

565 ms

style.min.css

style.min.css

185 ms

unsemantic-grid.min.css

unsemantic-grid.min.css

308 ms

style.min.css

style.min.css

338 ms

mobile.min.css

mobile.min.css

352 ms

js

js

58 ms

adsbygoogle.js

adsbygoogle.js

91 ms

adsbygoogle.js

adsbygoogle.js

92 ms

menu.min.js

menu.min.js

420 ms

flyradar24.jpg

flyradar24.jpg

230 ms

fly-radar-logo.png

fly-radar-logo.png

127 ms

fly-radar-24.png

fly-radar-24.png

131 ms

flyradar.jpg

flyradar.jpg

382 ms

flight-radar.jpg

flight-radar.jpg

246 ms

www.radarbox.com

www.radarbox.com

597 ms

rb24-94376cf4.css

rb24-94376cf4.css

29 ms

ol-7-5-2.js

ol-7-5-2.js

82 ms

waves_white.svg

waves_white.svg

52 ms

icon_go_to.svg

icon_go_to.svg

26 ms

airnav_radarbox_logo.svg

airnav_radarbox_logo.svg

48 ms

store_google.png

store_google.png

51 ms

store_apple.png

store_apple.png

47 ms

PTSans-Regular.otf

PTSans-Regular.otf

27 ms

polyfill.min.js

polyfill.min.js

36 ms

widget-315452c4.js

widget-315452c4.js

184 ms

Accessibility Review

flyradar.eu accessibility score

86

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

Best Practices

flyradar.eu 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

flyradar.eu SEO score

100

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

flyradar.eu

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