Report Summary

  • 9

    Performance

    Renders faster than
    23% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

midtown.nl

Hét All-in Family Resort van Nederland | Preston Palace

Page Load Speed

6.3 sec in total

First Response

939 ms

Resources Loaded

4.3 sec

Page Rendered

1 sec

About Website

Click here to check amazing Midtown content. Otherwise, check out these important facts you probably never knew about midtown.nl

Compleet verzorgd verblijf in All-in Family Resort Preston Palace is perfect voor families! Unieke faciliteiten, onbeperkt eten & drinken & alles onder één dak.

Visit midtown.nl

Key Findings

We analyzed Midtown.nl page load time and found that the first response time was 939 ms and then it took 5.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

midtown.nl performance score

9

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

28/100

10%

LCP (Largest Contentful Paint)

Value7.8 s

3/100

25%

SI (Speed Index)

Value14.6 s

1/100

10%

TBT (Total Blocking Time)

Value3,890 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.328

35/100

15%

TTI (Time to Interactive)

Value22.5 s

1/100

10%

Network Requests Diagram

www.prestonpalace.nl

939 ms

gtm.js

373 ms

tok2hao.css

379 ms

main.5c3fe6f0.css

205 ms

eum.min.js

122 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Midtown.nl, 26% (15 requests) were made to Prestonpalace.nl and 10% (6 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (2 sec) relates to the external source Arcbvmgvmp.cloudimg.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 198.3 kB (11%)

Content Size

1.7 MB

After Optimization

1.5 MB

In fact, the total size of Midtown.nl main page is 1.7 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. 70% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 194.3 kB

  • Original 218.5 kB
  • After minification 156.8 kB
  • After compression 24.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. This page needs HTML code to be minified as it can gain 61.8 kB, which is 28% 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 194.3 kB or 89% of the original size.

Image Optimization

-0%

Potential reduce by 325 B

  • Original 1.4 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. Midtown images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 853 B

  • Original 38.0 kB
  • After minification 38.0 kB
  • After compression 37.2 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

-4%

Potential reduce by 2.9 kB

  • Original 70.9 kB
  • After minification 70.8 kB
  • After compression 68.0 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. Midtown.nl has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 11 (22%)

Requests Now

51

After Optimization

40

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

Accessibility Review

midtown.nl accessibility score

88

Accessibility Issues

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

Links do not have a discernible name

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

midtown.nl 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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

midtown.nl SEO score

99

Search Engine Optimization Advices

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

    NL

  • Language Claimed

    NL

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Midtown.nl can be misinterpreted by Google and other search engines. Our service has detected that Dutch is used on the page, and it matches the claimed language. Our system also found out that Midtown.nl 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

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