6.1 sec in total
1.4 sec
4.5 sec
233 ms
Welcome to freiberg.de homepage info - get ready to check Freiberg best content for Germany right away, or after learning these important things about freiberg.de
Visit freiberg.deWe analyzed Freiberg.de page load time and found that the first response time was 1.4 sec and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
freiberg.de performance score
name
value
score
weighting
Value5.0 s
10/100
10%
Value7.5 s
4/100
25%
Value11.4 s
5/100
10%
Value1,600 ms
12/100
30%
Value0.064
97/100
15%
Value12.0 s
16/100
10%
1374 ms
509 ms
676 ms
379 ms
305 ms
Our browser made a total of 67 requests to load all elements on the main page. We found that all of those requests were addressed to Freiberg.de and no external sources were called. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Freiberg.de.
Page size can be reduced by 157.1 kB (17%)
911.6 kB
754.5 kB
In fact, the total size of Freiberg.de main page is 911.6 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. Only 10% of websites need less resources to load. Images take 758.7 kB which makes up the majority of the site volume.
Potential reduce by 21.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 21.2 kB or 76% of the original size.
Potential reduce by 42.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. Freiberg images are well optimized though.
Potential reduce by 47.9 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.9 kB or 68% of the original size.
Potential reduce by 45.6 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. Freiberg.de needs all CSS files to be minified and compressed as it can save up to 45.6 kB or 83% of the original size.
Number of requests can be reduced by 19 (29%)
66
47
The browser has sent 66 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Freiberg. 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 as a result speed up the page load time.
Webseite_B7D3F2486DC6F173C125759B0049C55E
1374 ms
styles.css
509 ms
jquery-1.3.1.min.js
676 ms
jquery.cookie.js
379 ms
fontSizer.js
305 ms
general.js
306 ms
contrast.js
417 ms
startpage.css
424 ms
cycle.js
424 ms
jquery.cycle.lite.js
596 ms
bg3.jpg
126 ms
logo.gif
123 ms
kontrast-icon-off.png
127 ms
ico_leichte_sprache.jpg
118 ms
logo_rundung.gif
130 ms
alte-elisabeth.jpg
463 ms
altstadt.jpg
623 ms
am_dom.jpg
572 ms
bergarchiv.jpg
612 ms
bergmaenner_schloss.jpg
658 ms
grabendurchblick.jpg
710 ms
johannesbad.jpg
748 ms
reiche_zeche_winter.jpg
812 ms
silbermannorgel.jpg
1064 ms
terra.jpg
888 ms
icon_navi_tourismus_kultur.jpg
852 ms
icon_navi_uni.jpg
867 ms
icon_navi_landkreis.jpg
918 ms
1pxhg2.jpg
992 ms
Webseite_B7D3F2486DC6F173C125759B0049C55E
2141 ms
icon_navi2_stadt2.jpg
998 ms
icon_navi2_ausschreibung.png
1013 ms
icon_navi2_wegweiser.jpg
1037 ms
icon_navi2_buergerbuero.jpg
1116 ms
icon_navi2_wirtschaft.jpg
1120 ms
ico_aufgabe.jpg
1126 ms
icon_navi2_partnerstadt.jpg
1156 ms
icon_navi2_stadtrat.jpg
1180 ms
icon_navi2_kinderparlament.jpg
1230 ms
icon_navi2_barrierefrei.jpg
1239 ms
buergersprechstunde.jpg
1279 ms
trenner_aktuelles.gif
1281 ms
LangeEinkaufsnacht.jpg
1404 ms
14_Das_Geheimnis_der_Hebamme.jpg
1433 ms
Ratssaal2_2013_Jungnickel.JPG
1488 ms
01_Fluechtlinge.JPG
1525 ms
Kron.jpg
1373 ms
Tuermel_StartseiteRedaktion.jpg
1467 ms
hundundkatz.jpg
1517 ms
RathausGlockenspiel.jpg
1564 ms
Logo_EFRE_2013.jpg
1599 ms
hg_aktuelles2.jpg
1295 ms
linie.gif
1192 ms
krueger_WEB.jpg
1212 ms
schnelllink_amtsblatt.jpg
1199 ms
schnelllink_uebernachtung_icon.jpg
1282 ms
schnelllink_stadtplan.jpg
1189 ms
schnelllink_stellenangebote.jpg
1172 ms
schnelllink_archiv.jpg
1146 ms
schnelllink_immobilien.jpg
1093 ms
schnelllink_wetter.jpg
1144 ms
twitter.jpg
1149 ms
BannerEhrungen190.jpg
1245 ms
BuchWerbung160.jpg
1125 ms
Logo_swg_wir_sind_freiberg_logo.jpg
1161 ms
footerhg2.jpg
1177 ms
styles_print.css
154 ms
freiberg.de accessibility score
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
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
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.
freiberg.de 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
Page has valid source maps
freiberg.de SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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
DE
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Freiberg.de can be misinterpreted by Google and other search engines. Our service has detected that German 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 Freiberg.de 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.
freiberg.de
Open Graph description is not detected on the main page of Freiberg. 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: