4.5 sec in total
332 ms
3.9 sec
288 ms
Welcome to marburg.de homepage info - get ready to check Marburg best content for Germany right away, or after learning these important things about marburg.de
Startseite Internet
Visit marburg.deWe analyzed Marburg.de page load time and found that the first response time was 332 ms and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
marburg.de performance score
name
value
score
weighting
Value5.5 s
6/100
10%
Value10.8 s
0/100
25%
Value8.9 s
15/100
10%
Value7,140 ms
0/100
30%
Value0.523
15/100
15%
Value13.6 s
11/100
10%
332 ms
795 ms
369 ms
314 ms
1229 ms
Our browser made a total of 52 requests to load all elements on the main page. We found that 98% of them (51 requests) were addressed to the original Marburg.de, 2% (1 request) were made to Stats.marburg.de. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Marburg.de.
Page size can be reduced by 368.7 kB (30%)
1.2 MB
852.6 kB
In fact, the total size of Marburg.de main page is 1.2 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. 35% of websites need less resources to load. Images take 810.3 kB which makes up the majority of the site volume.
Potential reduce by 162.4 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 162.4 kB or 88% of the original size.
Potential reduce by 39.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. Marburg images are well optimized though.
Potential reduce by 146.3 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 146.3 kB or 72% of the original size.
Potential reduce by 20.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. Marburg.de needs all CSS files to be minified and compressed as it can save up to 20.2 kB or 82% of the original size.
Number of requests can be reduced by 21 (43%)
49
28
The browser has sent 49 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Marburg. 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.
marburg.de
332 ms
www.marburg.de
795 ms
basic-20160218.css
369 ms
ReadSpeakerClassic.css
314 ms
basic-20160218.js
1229 ms
ReadSpeaker.js
322 ms
ReadSpeakerClassic.js
411 ms
ReadSpeaker.Styles.css
117 ms
ReadSpeaker.Core.js
188 ms
ReadSpeaker.pub.Config.js
466 ms
bg.svg
335 ms
head_bg.png
334 ms
suche.png
337 ms
sprite.png
340 ms
marburg_logo.png
338 ms
menu.png
341 ms
bild1.jpg
551 ms
sliderteaser_rot.png
367 ms
bild2.jpg
415 ms
sliderteaser_gruen.png
478 ms
bild3.jpg
655 ms
bild4.jpg
617 ms
sliderteaser_orange.png
611 ms
wellcomeslider2.jpg
844 ms
vorstellung_klimaschutzbecher_25_2_16_foto_philipp_hoeh_-900003703-23001-100.jpg
807 ms
marburger_strasse_1_kl_foto_heiko_krause_stadt_marb_-900003699-23001-100.jpg
711 ms
kommunalwahl_am_6_maerz_2016-900003298-23001-100.jpg
840 ms
slideprev.png
730 ms
slidenext.png
796 ms
aufruf_weihnachten_in_cappel_-900002938-23001-100.jpg
930 ms
campzaun_1_kl_foto_heiko_krause_stadt_marburg-900003710-23001-100.jpg
947 ms
verpixelt_schueler_spenden_woerterbuecher_an_gefluechtete_-900003709-23001-100.jpg
1076 ms
lsm.png
949 ms
startseite.png
947 ms
karte.png
949 ms
oe_zeiten.png
1037 ms
fav.png
1054 ms
face.png
1056 ms
newsle.png
1090 ms
oe_webcam.png
1058 ms
marburg_logo_fuss.png
1144 ms
icons_slider.png
1154 ms
icomoon.ttf
1127 ms
link_intern.png
1084 ms
foot.jpg
1134 ms
piwik.js
647 ms
overlay.png
908 ms
controls.png
923 ms
border.png
948 ms
loading_background.png
950 ms
loading.gif
980 ms
ReadSpeaker.lib.Facade.adapter.jquery.js
1016 ms
marburg.de 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
[aria-hidden="true"] elements contain focusable descendents
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
marburg.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
marburg.de SEO score
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
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 Marburg.de 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 Marburg.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.
marburg.de
Open Graph data is detected on the main page of Marburg. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: