Tools & Wizards About Us
wittmund.de screenshot

Report Summary

  • 61

    Performance

    Renders faster than
    76% of other websites

  • 99

    Accessibility

    Visual factors better than
    that of 96% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

wittmund.de

Startseite | Stadt Wittmund

Page Load Speed

5.1 sec in total

First Response

329 ms

Resources Loaded

4.5 sec

Page Rendered

275 ms

wittmund.de screenshot

About Website

Click here to check amazing Wittmund content for Germany. Otherwise, check out these important facts you probably never knew about wittmund.de

Startseite Internet

Visit wittmund.de

Key Findings

We analyzed Wittmund.de page load time and found that the first response time was 329 ms and then it took 4.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

wittmund.de performance score

61

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

21/100

10%

LCP (Largest Contentful Paint)

Value6.9 s

7/100

25%

SI (Speed Index)

Value5.4 s

57/100

10%

TBT (Total Blocking Time)

Value150 ms

95/100

30%

CLS (Cumulative Layout Shift)

Value0.006

100/100

15%

TTI (Time to Interactive)

Value5.0 s

76/100

10%

Network Requests Diagram

wittmund.de

329 ms

www.wittmund.de

785 ms

basic-27160.css

319 ms

57ca53a0-c61b-4e0c-89b7-e94c45664b6a.css

846 ms

basic-27160.js

697 ms

Our browser made a total of 28 requests to load all elements on the main page. We found that 61% of them (17 requests) were addressed to the original Wittmund.de, 39% (11 requests) were made to Fonts.nol-is.de. The less responsive or slowest element that took the longest time to load (2.5 sec) relates to the external source Fonts.nol-is.de.

Page Optimization Overview & Recommendations

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

Content Size

732.0 kB

After Optimization

623.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Wittmund.de main page is 732.0 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. 25% of websites need less resources to load. Images take 525.7 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 82.9 kB

  • Original 96.2 kB
  • After minification 94.4 kB
  • After compression 13.3 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 82.9 kB or 86% of the original size.

Image Optimization

-5%

Potential reduce by 26.0 kB

  • Original 525.7 kB
  • After minification 499.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. Wittmund images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 23 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 75 B

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

Requests Breakdown

We found no issues to fix!

Requests Now

16

After Optimization

16

  • Images
  • JavaScript
  • CSS

The browser has sent 16 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wittmund. According to our analytics all requests are already optimized.

Network Requests Diagram

wittmund.de

wittmund.de

329 ms

www.wittmund.de

www.wittmund.de

785 ms

basic-27160.css

basic-27160.css

319 ms

57ca53a0-c61b-4e0c-89b7-e94c45664b6a.css

57ca53a0-c61b-4e0c-89b7-e94c45664b6a.css

846 ms

basic-27160.js

basic-27160.js

697 ms

cookiedough_min.js

cookiedough_min.js

205 ms

logo.png

logo.png

208 ms

search.png

search.png

132 ms

head_background.png

head_background.png

133 ms

sprite.png

sprite.png

302 ms

banner900000027.jpg

banner900000027.jpg

408 ms

angekreuzter_kreis-900000370-22270-100.webp

angekreuzter_kreis-900000370-22270-100.webp

284 ms

50_jahre_kindergarten_klabauter_jpg-900001077-22270-100.webp

50_jahre_kindergarten_klabauter_jpg-900001077-22270-100.webp

500 ms

symbolbild_stellenausschreibung-900000367-22270-100.webp

symbolbild_stellenausschreibung-900000367-22270-100.webp

402 ms

freibad_isums_rutschen-900000189-22270-100.webp

freibad_isums_rutschen-900000189-22270-100.webp

443 ms

logo_foot.jpg

logo_foot.jpg

382 ms

banner_background.png

banner_background.png

336 ms

foot_background.png

foot_background.png

430 ms

roboto-v18-latin-ext-300.woff

roboto-v18-latin-ext-300.woff

102 ms

roboto-v18-latin-ext-100.woff

roboto-v18-latin-ext-100.woff

203 ms

roboto-v18-latin-ext-regular.woff

roboto-v18-latin-ext-regular.woff

406 ms

roboto-v18-latin-ext-500.woff

roboto-v18-latin-ext-500.woff

395 ms

roboto-v18-latin-ext-700.woff

roboto-v18-latin-ext-700.woff

407 ms

roboto-v18-latin-ext-900.woff

roboto-v18-latin-ext-900.woff

407 ms

fa-light-300.ttf

fa-light-300.ttf

2356 ms

fa-thin-100.ttf

fa-thin-100.ttf

2496 ms

fa-regular-400.ttf

fa-regular-400.ttf

2261 ms

fa-solid-900.ttf

fa-solid-900.ttf

2062 ms

Accessibility Review

wittmund.de accessibility score

99

Accessibility Issues

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

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

wittmund.de SEO score

91

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

wittmund.de

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