Tools & Wizards About Us
nordseeduggen.de screenshot

Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 30% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

nordseeduggen.de

Ferienwohnungen, Ferienhäuser und Apartments in St. Peter-Ording

Page Load Speed

145.4 sec in total

First Response

50 ms

Resources Loaded

144.9 sec

Page Rendered

427 ms

nordseeduggen.de screenshot

About Website

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

Seit mehr als 40 Jahren Ihr zuverlässiger Vermittler für Ferienwohnungen, Ferienhäuser und Apartments in St. Peter-Ording - Unterkünfte in allen Ortsteilen und Preislagen direkt vom Eigentümer.

Visit nordseeduggen.de

Key Findings

We analyzed Nordseeduggen.de page load time and found that the first response time was 50 ms and then it took 145.3 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 were 42 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

nordseeduggen.de performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

49/100

10%

LCP (Largest Contentful Paint)

Value14.2 s

0/100

25%

SI (Speed Index)

Value11.4 s

5/100

10%

TBT (Total Blocking Time)

Value1,940 ms

8/100

30%

CLS (Cumulative Layout Shift)

Value0.025

100/100

15%

TTI (Time to Interactive)

Value12.7 s

14/100

10%

Network Requests Diagram

www.nordseeduggen.de

50 ms

gtm.js

62 ms

bundle.css

28 ms

loader4.js

26 ms

appartement-vermittlung-duggen_896618

510 ms

Our browser made a total of 91 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Nordseeduggen.de, 74% (67 requests) were made to Umap.openstreetmap.fr and 16% (15 requests) were made to R.v-office.com. The less responsive or slowest element that took the longest time to load (73.4 sec) relates to the external source Umap.openstreetmap.fr.

Page Optimization Overview & Recommendations

Page size can be reduced by 51.8 kB (38%)

Content Size

134.6 kB

After Optimization

82.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Nordseeduggen.de main page is 134.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. 45% of websites need less resources to load. HTML takes 54.3 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 45.3 kB

  • Original 54.3 kB
  • After minification 37.2 kB
  • After compression 9.0 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. This page needs HTML code to be minified as it can gain 17.1 kB, which is 31% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 45.3 kB or 83% of the original size.

Image Optimization

-5%

Potential reduce by 2.5 kB

  • Original 53.0 kB
  • After minification 50.5 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. Nordseeduggen images are well optimized though.

JavaScript Optimization

-19%

Potential reduce by 417 B

  • Original 2.2 kB
  • After minification 2.2 kB
  • After compression 1.8 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 417 B or 19% of the original size.

CSS Optimization

-14%

Potential reduce by 3.6 kB

  • Original 25.2 kB
  • After minification 25.2 kB
  • After compression 21.5 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. Nordseeduggen.de needs all CSS files to be minified and compressed as it can save up to 3.6 kB or 14% of the original size.

Requests Breakdown

Number of requests can be reduced by 28 (68%)

Requests Now

41

After Optimization

13

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 41 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Nordseeduggen. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

www.nordseeduggen.de

www.nordseeduggen.de

50 ms

gtm.js

gtm.js

62 ms

bundle.css

bundle.css

28 ms

loader4.js

loader4.js

26 ms

appartement-vermittlung-duggen_896618

appartement-vermittlung-duggen_896618

510 ms

Logo.png

Logo.png

21 ms

gastfreundlich-icon.png

gastfreundlich-icon.png

25 ms

zentral-icon.png

zentral-icon.png

25 ms

family-icon.png

family-icon.png

29 ms

slider_familie.jpg

slider_familie.jpg

34 ms

strandurlaub-img.jpg

strandurlaub-img.jpg

28 ms

luxusurlaub-img.jpg

luxusurlaub-img.jpg

29 ms

hund-img.jpg

hund-img.jpg

29 ms

wellness-img.jpg

wellness-img.jpg

31 ms

aktivurlaub-img-1.jpg

aktivurlaub-img-1.jpg

30 ms

Tahoma.woff

Tahoma.woff

40 ms

Tahoma-Bold.woff

Tahoma-Bold.woff

33 ms

leaflet.f18ae622e307.css

leaflet.f18ae622e307.css

104 ms

MarkerCluster.7bc4f5bc3ef9.css

MarkerCluster.7bc4f5bc3ef9.css

206 ms

MarkerCluster.Default.0ba3d71ad098.css

MarkerCluster.Default.0ba3d71ad098.css

307 ms

Leaflet.EditInOSM.4973ef7d76c3.css

Leaflet.EditInOSM.4973ef7d76c3.css

308 ms

Control.MiniMap.min.f5616cda6e8e.css

Control.MiniMap.min.f5616cda6e8e.css

309 ms

leaflet.contextmenu.min.ab8f7859e8a9.css

leaflet.contextmenu.min.ab8f7859e8a9.css

309 ms

leaflet.toolbar.fe19968fc6d4.css

leaflet.toolbar.fe19968fc6d4.css

310 ms

Leaflet.Measurable.e0d4c475cd42.css

Leaflet.Measurable.e0d4c475cd42.css

309 ms

leaflet.fullscreen.6dd7f1493d15.css

leaflet.fullscreen.6dd7f1493d15.css

409 ms

L.Control.Locate.min.e6109be62f05.css

L.Control.Locate.min.e6109be62f05.css

409 ms

iconLayers.3c1ee6bd830e.css

iconLayers.3c1ee6bd830e.css

410 ms

vars.15f114c1f551.css

vars.15f114c1f551.css

410 ms

font.abdc7e1f8eb9.css

font.abdc7e1f8eb9.css

410 ms

icon.b95f24b2dff6.css

icon.b95f24b2dff6.css

411 ms

base.cc1fa0e664ed.css

base.cc1fa0e664ed.css

511 ms

content.f15630742242.css

content.f15630742242.css

509 ms

nav.4645edd0d02b.css

nav.4645edd0d02b.css

512 ms

map.bcb46f040987.css

map.bcb46f040987.css

514 ms

panel.ce30de7de96c.css

panel.ce30de7de96c.css

513 ms

7be080984d5b415b88b2628181dbac2a.min.js

7be080984d5b415b88b2628181dbac2a.min.js

14 ms

leaflet-src.esm.8061ab6fa5db.js

leaflet-src.esm.8061ab6fa5db.js

73384 ms

leaflet-configure.fffe72d95a6e.js

leaflet-configure.fffe72d95a6e.js

611 ms

de.12186b7faac0.js

de.12186b7faac0.js

619 ms

global.22b0e0e4cfa6.js

global.22b0e0e4cfa6.js

611 ms

Path.Drag.a0809fcb697e.js

Path.Drag.a0809fcb697e.js

619 ms

Leaflet.Editable.27dff66bb8c8.js

Leaflet.Editable.27dff66bb8c8.js

619 ms

leaflet-hash.4bcde8e8d544.js

leaflet-hash.4bcde8e8d544.js

0 ms

Leaflet.EditInOSM.6d630dfa5495.js

Leaflet.EditInOSM.6d630dfa5495.js

0 ms

Control.MiniMap.min.4c4b8e7e5ebf.js

Control.MiniMap.min.4c4b8e7e5ebf.js

73383 ms

csv2geojson.8e0381941f43.js

csv2geojson.8e0381941f43.js

73383 ms

togeojson.umd.95a2ea038c77.js

togeojson.umd.95a2ea038c77.js

73384 ms

osmtogeojson.9525e07370af.js

osmtogeojson.9525e07370af.js

73384 ms

Control.Loading.3cc734d7f8e8.js

Control.Loading.3cc734d7f8e8.js

73384 ms

leaflet.markercluster.0595019b4e3e.js

leaflet.markercluster.0595019b4e3e.js

73384 ms

leaflet.contextmenu.min.cdd16a0613b3.js

leaflet.contextmenu.min.cdd16a0613b3.js

73384 ms

leaflet.photon.f767efc7bd5a.js

leaflet.photon.f767efc7bd5a.js

73383 ms

GeoRSSToGeoJSON.e67aee5ce270.js

GeoRSSToGeoJSON.e67aee5ce270.js

73288 ms

leaflet-heat.7c49f3d195e1.js

leaflet-heat.7c49f3d195e1.js

73186 ms

Leaflet.fullscreen.min.17ff40b18ca8.js

Leaflet.fullscreen.min.17ff40b18ca8.js

73084 ms

leaflet.toolbar.de2e25d7cbe7.js

leaflet.toolbar.de2e25d7cbe7.js

73084 ms

Leaflet.FormBuilder.9d1b328e88a2.js

Leaflet.FormBuilder.9d1b328e88a2.js

73082 ms

Leaflet.Measurable.4c788e494421.js

Leaflet.Measurable.4c788e494421.js

73082 ms

togpx.549cf9914499.js

togpx.549cf9914499.js

73082 ms

iconLayers.73b220e72069.js

iconLayers.73b220e72069.js

73082 ms

tokml.bb3f95178d5d.js

tokml.bb3f95178d5d.js

72983 ms

L.Control.Locate.min.63a409b2ab41.js

L.Control.Locate.min.63a409b2ab41.js

72982 ms

colorbrewer.c152c04ee637.js

colorbrewer.c152c04ee637.js

72982 ms

simple-statistics.min.227703e75087.js

simple-statistics.min.227703e75087.js

72981 ms

umap.core.3e12fea9b9bf.js

umap.core.3e12fea9b9bf.js

72981 ms

umap.autocomplete.47016c5586cc.js

umap.autocomplete.47016c5586cc.js

72981 ms

umap.popup.7581e9fea85f.js

umap.popup.7581e9fea85f.js

72881 ms

umap.forms.7df10b15d20e.js

umap.forms.7df10b15d20e.js

72881 ms

umap.icon.9ac8f352545b.js

umap.icon.9ac8f352545b.js

72879 ms

umap.features.4e15a22fc4cd.js

umap.features.4e15a22fc4cd.js

72879 ms

umap.permissions.9fa9696b0d24.js

umap.permissions.9fa9696b0d24.js

72875 ms

bundle.min.js

bundle.min.js

10 ms

umap.datalayer.permissions.8cfe43fe238b.js

umap.datalayer.permissions.8cfe43fe238b.js

72874 ms

umap.layer.118cc1a72651.js

umap.layer.118cc1a72651.js

72779 ms

umap.controls.3d30884eabc9.js

umap.controls.3d30884eabc9.js

72780 ms

35 ms

umap.slideshow.22c48542361f.js

umap.slideshow.22c48542361f.js

72772 ms

46 ms

40 ms

umap.tableeditor.c34e1f816383.js

umap.tableeditor.c34e1f816383.js

72767 ms

umap.importer.2196a663afc7.js

umap.importer.2196a663afc7.js

72767 ms

12736 ms

65 ms

umap.share.85b9f2a4dd52.js

umap.share.85b9f2a4dd52.js

0 ms

umap.730c71120411.js

umap.730c71120411.js

70471 ms

umap.ui.cdd5d3aae8c3.js

umap.ui.cdd5d3aae8c3.js

70471 ms

fragment.06ec6d3af817.js

fragment.06ec6d3af817.js

70471 ms

FiraSans-Light.29430787e85c.woff

FiraSans-Light.29430787e85c.woff

70470 ms

FiraSans-SemiBold.defc482e83c8.woff

FiraSans-SemiBold.defc482e83c8.woff

70471 ms

bundle.js

bundle.js

77 ms

Accessibility Review

nordseeduggen.de accessibility score

65

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

Buttons do not have an accessible name

High

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

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

nordseeduggen.de best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

nordseeduggen.de SEO score

85

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

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

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

nordseeduggen.de

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