2.7 sec in total
229 ms
2.3 sec
161 ms
Click here to check amazing Fr 24 content for Tunisia. Otherwise, check out these important facts you probably never knew about fr24.com
Flightradar24 is the best live flight tracker that shows air traffic in real time. Best coverage and cool features!
Visit fr24.comWe analyzed Fr24.com page load time and found that the first response time was 229 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
fr24.com performance score
name
value
score
weighting
Value6.6 s
2/100
10%
Value23.3 s
0/100
25%
Value18.6 s
0/100
10%
Value141,130 ms
0/100
30%
Value0.689
7/100
15%
Value176.7 s
0/100
10%
229 ms
711 ms
41 ms
52 ms
84 ms
Our browser made a total of 150 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Fr24.com, 32% (48 requests) were made to Maps.google.com and 30% (45 requests) were made to Flightradar24.com. The less responsive or slowest element that took the longest time to load (711 ms) relates to the external source Flightradar24.com.
Page size can be reduced by 3.0 MB (73%)
4.1 MB
1.1 MB
In fact, the total size of Fr24.com main page is 4.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. 75% 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.4 MB which makes up the majority of the site volume.
Potential reduce by 279.3 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 70.7 kB, which is 22% 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 279.3 kB or 85% of the original size.
Potential reduce by 2.4 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. Fr 24 images are well optimized though.
Potential reduce by 2.4 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.4 MB or 72% of the original size.
Potential reduce by 283.1 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. Fr24.com needs all CSS files to be minified and compressed as it can save up to 283.1 kB or 81% of the original size.
Number of requests can be reduced by 113 (77%)
146
33
The browser has sent 146 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fr 24. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 65 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
fr24.com
229 ms
www.flightradar24.com
711 ms
jquery.ui.slider.css
41 ms
screen_new.css
52 ms
font-awesome.min.css
84 ms
bootstrap.min.css
74 ms
nav-top.css
78 ms
jquery.min.js
122 ms
jquery-ui.min.js
162 ms
moment.min.js
98 ms
LocalStorage.js
78 ms
SessionStorage.js
78 ms
Navigation.js
96 ms
prototypes.js
78 ms
js
103 ms
angular.min.js
207 ms
angular-resource.min.js
205 ms
timeline.min.js
106 ms
tracks.js
102 ms
airport_page.js
101 ms
highcharts.js
114 ms
bootstrap.min.js
77 ms
jquery.ui.selectmenu.js
100 ms
jquery.history.min.js
116 ms
aircraft.marker.js
120 ms
weather.js
117 ms
js_new.js
154 ms
Cesium.js
257 ms
cockpit_view.js
116 ms
cockpit_view.css
126 ms
business.js
119 ms
infobox.js
119 ms
nite-overlay.js
123 ms
app.js
124 ms
controllers.js
123 ms
directives.js
132 ms
services.js
132 ms
filters.js
127 ms
viewMenu.js
131 ms
css
97 ms
displaySideView.css
45 ms
widgets.css
41 ms
common.js
14 ms
util.js
39 ms
infowindow.js
37 ms
loading_32.gif
28 ms
pixel.png
30 ms
0.png
28 ms
app_store.svg
28 ms
google_play.svg
31 ms
img.gif
13 ms
logged_out.svg
14 ms
gpt.js
250 ms
adsbygoogle.js
199 ms
widgets.js
571 ms
platform.js
252 ms
all.js
590 ms
ga.js
251 ms
planedata
628 ms
617 ms
mediafeed
583 ms
map.js
46 ms
poly.js
77 ms
overlay.js
43 ms
x.svg
75 ms
fontawesome-webfont.woff
76 ms
ca-pub-0223260809600052.js
46 ms
zrt_lookup.html
170 ms
show_ads_impl.js
171 ms
onion.js
20 ms
list
543 ms
openhand_8_8.cur
259 ms
stats.js
112 ms
controls.js
141 ms
pubads_impl_82.js
370 ms
__utm.gif
191 ms
cb=gapi.loaded_0
179 ms
cb=gapi.loaded_1
182 ms
fastbutton
401 ms
transparent.png
263 ms
ViewportInfoService.GetViewportInfo
396 ms
undo_poly.png
226 ms
ads
313 ms
css
96 ms
osd.js
70 ms
google4.png
93 ms
mapcnt6.png
167 ms
ads
306 ms
postmessageRelay
247 ms
tmapctrl4.png
124 ms
ads
303 ms
ads
261 ms
__utm.gif
132 ms
238 ms
cb=gapi.loaded_0
80 ms
cb=gapi.loaded_1
80 ms
xd_arbiter.php
320 ms
container.html
117 ms
vt
55 ms
vt
50 ms
vt
44 ms
vt
63 ms
vt
63 ms
vt
62 ms
vt
64 ms
vt
62 ms
vt
73 ms
vt
74 ms
vt
73 ms
vt
72 ms
vt
73 ms
vt
72 ms
vt
81 ms
vt
80 ms
vt
80 ms
vt
79 ms
vt
80 ms
vt
79 ms
vt
94 ms
vt
93 ms
vt
94 ms
vt
95 ms
vt
94 ms
vt
92 ms
vt
165 ms
vt
164 ms
vt
162 ms
vt
163 ms
vt
162 ms
vt
161 ms
vt
169 ms
vt
169 ms
vt
168 ms
vt
168 ms
3193398744-postmessagerelay.js
71 ms
rpc:shindig_random.js
70 ms
vt
131 ms
marker.js
127 ms
css
30 ms
m_js_controller.js
17 ms
abg.js
59 ms
cb=gapi.loaded_0
80 ms
favicon
90 ms
googlelogo_color_112x36dp.png
97 ms
nessie_icon_thin_arrow_big_white.png
69 ms
s
63 ms
x_button_blue2.png
41 ms
AuthenticationService.Authenticate
24 ms
airportMarker.png
14 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
13 ms
fr24.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
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.
fr24.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
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
fr24.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 Fr24.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 Fr24.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.
fr24.com
Open Graph description is not detected on the main page of Fr 24. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: