Tools & Wizards About Us
marburg.de screenshot

Report Summary

  • 28

    Performance

    Renders faster than
    48% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

marburg.de

Startseite | Stadt Marburg

Page Load Speed

22.4 sec in total

First Response

349 ms

Resources Loaded

21.7 sec

Page Rendered

338 ms

marburg.de screenshot

About Website

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.de

Key Findings

We analyzed Marburg.de page load time and found that the first response time was 349 ms and then it took 22 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

marburg.de performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

13/100

10%

LCP (Largest Contentful Paint)

Value5.8 s

16/100

25%

SI (Speed Index)

Value5.7 s

51/100

10%

TBT (Total Blocking Time)

Value980 ms

28/100

30%

CLS (Cumulative Layout Shift)

Value0.379

28/100

15%

TTI (Time to Interactive)

Value7.5 s

47/100

10%

Network Requests Diagram

marburg.de

349 ms

www.marburg.de

877 ms

basic-20240412.css

351 ms

80ff9347-63ee-45be-b24c-df261614077c.css

978 ms

basic-20240412.js

786 ms

Our browser made a total of 51 requests to load all elements on the main page. We found that 94% of them (48 requests) were addressed to the original Marburg.de, 4% (2 requests) were made to Fonts.nol-is.de and 2% (1 request) were made to Pls.marburg.de. The less responsive or slowest element that took the longest time to load (19.5 sec) relates to the external source Pls.marburg.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 273.1 kB (15%)

Content Size

1.9 MB

After Optimization

1.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Marburg.de main page is 1.9 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 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 203.7 kB

  • Original 231.2 kB
  • After minification 226.7 kB
  • After compression 27.5 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 203.7 kB or 88% of the original size.

Image Optimization

-5%

Potential reduce by 69.4 kB

  • Original 1.5 MB
  • After minification 1.4 MB

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.

JavaScript Optimization

-1%

Potential reduce by 13 B

  • Original 1.7 kB
  • After minification 1.7 kB
  • After compression 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.

CSS Optimization

-0%

Potential reduce by 41 B

  • Original 107.8 kB
  • After minification 107.8 kB
  • After compression 107.8 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 has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 6 (13%)

Requests Now

46

After Optimization

40

  • Images
  • JavaScript
  • CSS

The browser has sent 46 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 and as a result speed up the page load time.

Network Requests Diagram

marburg.de

marburg.de

349 ms

www.marburg.de

www.marburg.de

877 ms

basic-20240412.css

basic-20240412.css

351 ms

80ff9347-63ee-45be-b24c-df261614077c.css

80ff9347-63ee-45be-b24c-df261614077c.css

978 ms

basic-20240412.js

basic-20240412.js

786 ms

cookiedough_min.js

cookiedough_min.js

226 ms

head_bg.png

head_bg.png

116 ms

marburg_logo_neu.svg

marburg_logo_neu.svg

115 ms

menu.png

menu.png

117 ms

sprite.png

sprite.png

217 ms

flagge.png

flagge.png

227 ms

suche.png

suche.png

230 ms

bild1.jpg

bild1.jpg

441 ms

sliderteaser_rot.png

sliderteaser_rot.png

445 ms

bild2.jpg

bild2.jpg

668 ms

sliderteaser_gruen.png

sliderteaser_gruen.png

448 ms

bild3.jpg

bild3.jpg

339 ms

wr56_012_marburg_kampagne_banner_website_210209.jpg

wr56_012_marburg_kampagne_banner_website_210209.jpg

572 ms

sliderteaser_blau.png

sliderteaser_blau.png

453 ms

eph_nachtakzente.jpg

eph_nachtakzente.jpg

887 ms

marburg_zeigt_respekt_-900027906-23001-100.jpg

marburg_zeigt_respekt_-900027906-23001-100.jpg

668 ms

move35_key_visual_2023_neu_mit_hintergrund_ausschnitt_-900026683-23001-100.jpg

move35_key_visual_2023_neu_mit_hintergrund_ausschnitt_-900026683-23001-100.jpg

571 ms

jhv_ffw_marburg_2024_foto_thomas_hummler_dokumentator_-900027898-23001-100.jpg

jhv_ffw_marburg_2024_foto_thomas_hummler_dokumentator_-900027898-23001-100.jpg

571 ms

slideprev.png

slideprev.png

674 ms

slidenext.png

slidenext.png

677 ms

drei_personen_halten_digitalisierungsobjekte_in_ihren_-900027889-23001-100.jpg

drei_personen_halten_digitalisierungsobjekte_in_ihren_-900027889-23001-100.jpg

678 ms

vier_frauen_spielen_boule_neben_dem_bewegungsbus_-900027886-23001-100.jpg

vier_frauen_spielen_boule_neben_dem_bewegungsbus_-900027886-23001-100.jpg

782 ms

wahlamt_foto_patricia_graehling_stadt_marburg_jpg-900027795-23001-100.jpg

wahlamt_foto_patricia_graehling_stadt_marburg_jpg-900027795-23001-100.jpg

781 ms

online_wahlschein_beantragen-900002499-23001-31.jpg

online_wahlschein_beantragen-900002499-23001-31.jpg

786 ms

fachkraefte_kampagne_2023_2_ausschnitt-900025700-23001-31.jpg

fachkraefte_kampagne_2023_2_ausschnitt-900025700-23001-31.jpg

789 ms

online_dienstleistungen_button-900016075-23001-31.jpg

online_dienstleistungen_button-900016075-23001-31.jpg

790 ms

move_35_key_visual_des_mobilitaets_und_verkehrskonzep_-900026108-23001-31.jpg

move_35_key_visual_des_mobilitaets_und_verkehrskonzep_-900026108-23001-31.jpg

894 ms

lahnimpressionen_blick_ueber_die_lahn_auf_die_haeuser_a_-900024805-23001-31.jpg

lahnimpressionen_blick_ueber_die_lahn_auf_die_haeuser_a_-900024805-23001-31.jpg

896 ms

lsm.png

lsm.png

899 ms

startseite.png

startseite.png

902 ms

karte.png

karte.png

902 ms

oe_zeiten.png

oe_zeiten.png

998 ms

fav.png

fav.png

1007 ms

podcast.png

podcast.png

1008 ms

face.png

face.png

1013 ms

twitter.png

twitter.png

1013 ms

instagram.png

instagram.png

1014 ms

pls-infobox.php

pls-infobox.php

19516 ms

nolisicon.woff

nolisicon.woff

490 ms

icomoon.ttf

icomoon.ttf

1014 ms

newsle.png

newsle.png

1017 ms

oe_webcam.png

oe_webcam.png

1017 ms

marburg_logo_fuss.png

marburg_logo_fuss.png

919 ms

icons_slider.png

icons_slider.png

909 ms

link_intern.png

link_intern.png

904 ms

foot.jpg

foot.jpg

889 ms

Accessibility Review

marburg.de accessibility score

93

Accessibility Issues

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

High

[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

High

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

marburg.de best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

marburg.de SEO score

89

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    DE

  • Language Claimed

    DE

  • Encoding

    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.

Social Sharing Optimization

marburg.de

Open Graph description is not detected on the main page of Marburg. 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: