2.2 sec in total
460 ms
1.6 sec
187 ms
Visit aprs.fi now to see the best up-to-date APRS content for Germany and also check out these interesting facts you probably never knew about aprs.fi
Visit aprs.fiWe analyzed Aprs.fi page load time and found that the first response time was 460 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
aprs.fi performance score
name
value
score
weighting
Value3.7 s
30/100
10%
Value6.4 s
9/100
25%
Value4.6 s
70/100
10%
Value970 ms
28/100
30%
Value0
100/100
15%
Value6.4 s
60/100
10%
460 ms
34 ms
111 ms
514 ms
354 ms
Our browser made a total of 65 requests to load all elements on the main page. We found that 38% of them (25 requests) were addressed to the original Aprs.fi, 46% (30 requests) were made to Tile.openstreetmap.org and 6% (4 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (671 ms) belongs to the original domain Aprs.fi.
Page size can be reduced by 232.3 kB (17%)
1.4 MB
1.2 MB
In fact, the total size of Aprs.fi main page is 1.4 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. 60% of websites need less resources to load. Images take 889.9 kB which makes up the majority of the site volume.
Potential reduce by 21.8 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 21.8 kB or 77% of the original size.
Potential reduce by 23.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. APRS images are well optimized though.
Potential reduce by 47.0 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 47.0 kB or 16% of the original size.
Potential reduce by 140.2 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. Aprs.fi needs all CSS files to be minified and compressed as it can save up to 140.2 kB or 85% of the original size.
Number of requests can be reduced by 22 (34%)
64
42
The browser has sent 64 CSS, Javascripts, AJAX and image requests in order to completely render the main page of APRS. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
aprs.fi
460 ms
ga.js
34 ms
gpt.js
111 ms
bootstrap.min.css
514 ms
bootstrap-reboot.min.css
354 ms
maps.css
359 ms
map_common.css
357 ms
calendar.css
356 ms
leaflet.css
52 ms
jquery.min.js
50 ms
bootstrap.min.js
558 ms
transform.js
455 ms
lib.js
461 ms
leaflet.js
70 ms
constants.js
461 ms
usng.js
464 ms
date.js
586 ms
maps_leaflet.js
671 ms
calendar.js
586 ms
__utm.gif
12 ms
pubads_impl.js
22 ms
close.gif
104 ms
map_bg_right.png
105 ms
aprsfi-web-sprite.png
105 ms
aprsfi-logo-mid-tr.png
106 ms
button_bg.png
104 ms
container.html
32 ms
northamerica
104 ms
__utm.gif
46 ms
782.png
41 ms
sm.js
109 ms
deferred_leaflet.js
113 ms
deferred_nonmob_leaflet.js
113 ms
maphilight.js
113 ms
timezone-picker.js
112 ms
782.png
20 ms
781.png
20 ms
781.png
18 ms
783.png
18 ms
783.png
21 ms
782.png
25 ms
782.png
24 ms
781.png
24 ms
781.png
23 ms
783.png
24 ms
783.png
36 ms
780.png
35 ms
780.png
36 ms
784.png
35 ms
784.png
36 ms
780.png
34 ms
780.png
38 ms
782.png
36 ms
782.png
37 ms
784.png
36 ms
784.png
38 ms
781.png
38 ms
781.png
41 ms
783.png
43 ms
783.png
40 ms
780.png
41 ms
780.png
38 ms
784.png
39 ms
784.png
42 ms
__utm.gif
13 ms
aprs.fi accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Form elements do not have associated labels
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.
aprs.fi 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
Page has valid source maps
aprs.fi SEO score
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 doesn't use legible font sizes
Tap targets are not sized appropriately
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Aprs.fi can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Aprs.fi 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.
aprs.fi
Open Graph description is not detected on the main page of APRS. 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: