Tools & Wizards About Us

Report Summary

  • 28

    Performance

    Renders faster than
    47% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 81

    SEO

    Google-friendlier than
    42% of websites

dublin.nl

Stedentrip Dublin | de Jong Intra Vakanties

Page Load Speed

5.1 sec in total

First Response

276 ms

Resources Loaded

3.8 sec

Page Rendered

1 sec

About Website

Welcome to dublin.nl homepage info - get ready to check Dublin best content right away, or after learning these important things about dublin.nl

Ga op stedentrip naar Dublin met de Jong Intra Vakanties. Bekijk de mogelijkheden en boek gemakkelijk via onze website.

Visit dublin.nl

Key Findings

We analyzed Dublin.nl page load time and found that the first response time was 276 ms and then it took 4.9 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

dublin.nl performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

50/100

10%

LCP (Largest Contentful Paint)

Value9.9 s

0/100

25%

SI (Speed Index)

Value5.4 s

57/100

10%

TBT (Total Blocking Time)

Value2,010 ms

7/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value16.2 s

5/100

10%

Network Requests Diagram

dublin.nl

276 ms

dublin.nl

496 ms

dublin

654 ms

master.2ba6e756d35e2b53700b.css

15 ms

www.c1db44216d5519a60b2a.css

10 ms

Our browser made a total of 60 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Dublin.nl, 58% (35 requests) were made to Dejongintra.nl and 37% (22 requests) were made to Content.dejongintra.nl. The less responsive or slowest element that took the longest time to load (2.4 sec) relates to the external source Content.dejongintra.nl.

Page Optimization Overview & Recommendations

Page size can be reduced by 128.5 kB (30%)

Content Size

421.8 kB

After Optimization

293.4 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Dublin.nl main page is 421.8 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. 60% of websites need less resources to load. Javascripts take 249.5 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 116.2 kB

  • Original 143.7 kB
  • After minification 138.0 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 116.2 kB or 81% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 28.7 kB
  • After minification 28.7 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. Dublin images are well optimized though.

JavaScript Optimization

-5%

Potential reduce by 12.2 kB

  • Original 249.5 kB
  • After minification 249.5 kB
  • After compression 237.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. This website has mostly compressed JavaScripts.

Requests Breakdown

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

Requests Now

57

After Optimization

44

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

dublin.nl accessibility score

83

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-*] attributes do not match their roles

High

ARIA input fields do not have accessible names

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

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

dublin.nl best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

dublin.nl SEO score

81

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Document doesn't have a valid hreflang

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

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dublin.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 Dublin.nl main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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