2.4 sec in total
300 ms
2 sec
148 ms
Visit freifunk.net now to see the best up-to-date Freifunk content for Germany and also check out these interesting facts you probably never knew about freifunk.net
Freifunk steht für freie Kommunikation in digitalen Datennetzen
Visit freifunk.netWe analyzed Freifunk.net page load time and found that the first response time was 300 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
freifunk.net performance score
name
value
score
weighting
Value4.1 s
22/100
10%
Value4.7 s
33/100
25%
Value4.5 s
72/100
10%
Value90 ms
99/100
30%
Value0
100/100
15%
Value5.0 s
76/100
10%
300 ms
474 ms
176 ms
360 ms
269 ms
Our browser made a total of 59 requests to load all elements on the main page. We found that 98% of them (58 requests) were addressed to the original Freifunk.net, 2% (1 request) were made to Piwik.freifunk.net. The less responsive or slowest element that took the longest time to load (733 ms) belongs to the original domain Freifunk.net.
Page size can be reduced by 67.4 kB (12%)
558.5 kB
491.1 kB
In fact, the total size of Freifunk.net main page is 558.5 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. 40% of websites need less resources to load. CSS take 175.9 kB which makes up the majority of the site volume.
Potential reduce by 44.1 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 44.1 kB or 76% of the original size.
Potential reduce by 15.8 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. Freifunk images are well optimized though.
Potential reduce by 1.6 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.
Potential reduce by 6.0 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. Freifunk.net has all CSS files already compressed.
Number of requests can be reduced by 36 (64%)
56
20
The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Freifunk. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.
freifunk.net
300 ms
freifunk.net
474 ms
MyFontsWebfontsOrderM4221928.css
176 ms
11f866b8_ai1ec_parsed_css.css
360 ms
wppb.css
269 ms
style.min.css
368 ms
grid-style2.css
280 ms
styles.css
279 ms
styles.css
282 ms
bootstrap.css
357 ms
shortcodes.css
372 ms
font-awesome.min.css
373 ms
wp-event-aggregator.css
375 ms
style.min.css
446 ms
style.css
449 ms
blocks.css
447 ms
dashicons.min.css
560 ms
reset.css
467 ms
twentytwentytwo.css
468 ms
front.css
536 ms
jquery.min.js
628 ms
jquery-migrate.min.js
538 ms
bootstrap-collapse.js
565 ms
bootstrap-transition.js
565 ms
embed.js
641 ms
cache.js
627 ms
navigation.js
652 ms
front.min.js
654 ms
wppb_animate.js
575 ms
index.js
639 ms
index.js
639 ms
wp-polyfill-inert.min.js
644 ms
regenerator-runtime.min.js
667 ms
wp-polyfill.min.js
670 ms
dom-ready.min.js
671 ms
hooks.min.js
728 ms
i18n.min.js
728 ms
a11y.min.js
733 ms
mcjs.min.js
670 ms
logo_freifunknet.png
183 ms
en.png
182 ms
de.png
235 ms
video.jpg
238 ms
map.png
330 ms
aufzaehlung_pfeile.png
271 ms
31895789206_93ae1ed3c6_k-1-e1698411515522.jpg
275 ms
pfeil_klein.png
274 ms
rss.png
324 ms
mailingliste.png
327 ms
radio.png
365 ms
api.png
367 ms
pads.png
368 ms
subdomain.png
413 ms
audio_text_chats.png
416 ms
blog1.png
418 ms
icon_social.png
458 ms
cc.png
460 ms
piwik.js
589 ms
24CF2E_0_0.woff
440 ms
freifunk.net 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.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
freifunk.net best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
freifunk.net SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
Tap targets are not sized appropriately
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Freifunk.net can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it matches the claimed language. Our system also found out that Freifunk.net 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.
freifunk.net
Open Graph data is detected on the main page of Freifunk. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: