71.7 sec in total
318 ms
64.2 sec
7.2 sec
Welcome to flightradar24.com homepage info - get ready to check Flightradar24 best content for United States right away, or after learning these important things about flightradar24.com
Flightradar24 is the best live flight tracker that shows air traffic in real time. Best coverage and cool features!
Visit flightradar24.comWe analyzed Flightradar24.com page load time and found that the first response time was 318 ms and then it took 71.4 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there were 6 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
flightradar24.com performance score
name
value
score
weighting
Value6.3 s
3/100
10%
Value23.7 s
0/100
25%
Value16.9 s
0/100
10%
Value3,250 ms
2/100
30%
Value0.689
7/100
15%
Value29.0 s
0/100
10%
318 ms
1037 ms
665 ms
3260 ms
759 ms
Our browser made a total of 105 requests to load all elements on the main page. We found that 56% of them (59 requests) were addressed to the original Flightradar24.com, 10% (11 requests) were made to Maps.google.com and 9% (9 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (24.3 sec) relates to the external source Ssl.google-analytics.com.
Page size can be reduced by 3.1 MB (49%)
6.3 MB
3.2 MB
In fact, the total size of Flightradar24.com main page is 6.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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 3.1 MB which makes up the majority of the site volume.
Potential reduce by 328.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 328.9 kB or 81% of the original size.
Potential reduce by 36.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. Flightradar24 images are well optimized though.
Potential reduce by 2.0 MB
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 2.0 MB or 66% of the original size.
Potential reduce by 693.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. Flightradar24.com needs all CSS files to be minified and compressed as it can save up to 693.7 kB or 83% of the original size.
Number of requests can be reduced by 68 (78%)
87
19
The browser has sent 87 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Flightradar24. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 56 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
flightradar24.com
318 ms
www.flightradar24.com
1037 ms
jquery.ui.slider.css
665 ms
font-awesome.min.css
3260 ms
bootstrap.min.css
759 ms
screen_new.css
2467 ms
nav-top.css
2420 ms
view-menu.css
3174 ms
jquery.min.js
3677 ms
jquery-ui.min.js
3802 ms
moment.min.js
3676 ms
moment-duration-format.min.js
3675 ms
LocalStorage.js
3194 ms
SessionStorage.js
3133 ms
Navigation.js
3132 ms
prototypes.js
3112 ms
flickity.min.css
3568 ms
flickity.pkgd.min.js
3521 ms
js
3620 ms
angular.min.js
3743 ms
angular-resource.min.js
3743 ms
app.js
3086 ms
controllers.js
3618 ms
directives.js
3564 ms
services.js
3613 ms
filters.js
3389 ms
timeline.min.js
3388 ms
tracks.js
3439 ms
panel.airport.desktop.js
3513 ms
highcharts.js
3438 ms
bootstrap.min.js
3513 ms
jquery.ui.selectmenu.js
3514 ms
jquery.history.min.js
3464 ms
aircraft.marker.js
3465 ms
tooltip.js
3464 ms
airmet_query.js
3514 ms
weather_tiles.js
5001 ms
lightning.js
3514 ms
navdata_layer.js
3513 ms
weather.js
3616 ms
js_new.js
3513 ms
Cesium.js
6259 ms
cockpit_view.js
5851 ms
cockpit_view.css
5850 ms
widgets.css
5850 ms
business.js
5627 ms
infobox.js
5626 ms
nite-overlay.js
6008 ms
panel.airport.desktop.css
5834 ms
displaySideView.css
5719 ms
delays.css
5574 ms
promoSlider.css
4149 ms
css
1503 ms
viewMenu.js
3539 ms
delaysView.js
3397 ms
promoSlider.js
3396 ms
fetch.min.js
735 ms
npo.js
615 ms
common.js
11487 ms
util.js
11717 ms
infowindow.js
12753 ms
stats.js
1025 ms
loading_32.gif
1037 ms
pixel.png
1036 ms
0.png
852 ms
click-loader.gif
1084 ms
app_store.svg
1084 ms
google_play.svg
1080 ms
no_airline_logo.png
1083 ms
login_unactive_2px-white.svg
1282 ms
AuthenticationService.Authenticate
509 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
706 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
1135 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
1169 ms
Zd2E9abXLFGSr9G3YK2MsDR-eWpsHSw83BRsAQElGgc.ttf
949 ms
b9QBgL0iMZfDSpmcXcE8nDokq8qT6AIiNJ07Vf_NrVA.ttf
949 ms
gpt.js
17598 ms
adsbygoogle.js
21129 ms
widgets.js
20893 ms
platform.js
20893 ms
all.js
20893 ms
ga.js
24303 ms
1504605222
0 ms
site-svg
9833 ms
map-menu-delays
14041 ms
planedata
13017 ms
16442 ms
mediafeed
11103 ms
10092 ms
map.js
6686 ms
poly.js
6684 ms
overlay.js
12499 ms
fontawesome-webfont.woff
10316 ms
pubads_impl_147.js
10786 ms
onion.js
2141 ms
list
3983 ms
openhand_8_8.cur
7127 ms
transparent.png
6149 ms
ViewportInfoService.GetViewportInfo
5389 ms
controls.js
5074 ms
marker.js
1973 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
1231 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
1230 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
1229 ms
undo_poly.png
1015 ms
flightradar24.com accessibility score
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
button, link, and menuitem elements do not have accessible names.
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
flightradar24.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
flightradar24.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Document uses legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Flightradar24.com 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 Flightradar24.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.
flightradar24.com
Open Graph data is detected on the main page of Flightradar24. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: