Tools & Wizards About Us
web2.dublinairport.com screenshot

Report Summary

  • 33

    Performance

    Renders faster than
    53% of other websites

  • 64

    Accessibility

    Visual factors better than
    that of 29% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

web2.dublinairport.com

Dublin Airport - Welcome to Dublin Airport Official Website

Page Load Speed

2.4 sec in total

First Response

148 ms

Resources Loaded

1.7 sec

Page Rendered

572 ms

web2.dublinairport.com screenshot

About Website

Click here to check amazing Web 2 Dublin Airport content for Ireland. Otherwise, check out these important facts you probably never knew about web2.dublinairport.com

Official Dublin airport website. Live flight times and updates, arrivals and departures, news, information, VIP services and car parking.

Visit web2.dublinairport.com

Key Findings

We analyzed Web2.dublinairport.com page load time and found that the first response time was 148 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

web2.dublinairport.com performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

24/100

10%

LCP (Largest Contentful Paint)

Value6.9 s

6/100

25%

SI (Speed Index)

Value6.4 s

41/100

10%

TBT (Total Blocking Time)

Value940 ms

29/100

30%

CLS (Cumulative Layout Shift)

Value0.072

96/100

15%

TTI (Time to Interactive)

Value10.9 s

21/100

10%

Network Requests Diagram

web2.dublinairport.com

148 ms

web2.dublinairport.com

435 ms

gulp_default.min.css

276 ms

ScriptResource.axd

404 ms

ScriptResource.axd

302 ms

Our browser made a total of 20 requests to load all elements on the main page. We found that 70% of them (14 requests) were addressed to the original Web2.dublinairport.com, 15% (3 requests) were made to Cdn-ukwest.onetrust.com and 5% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (435 ms) belongs to the original domain Web2.dublinairport.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 156.2 kB (40%)

Content Size

390.5 kB

After Optimization

234.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Web2.dublinairport.com main page is 390.5 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. HTML takes 194.8 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 155.3 kB

  • Original 194.8 kB
  • After minification 156.7 kB
  • After compression 39.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. This page needs HTML code to be minified as it can gain 38.1 kB, which is 20% 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 155.3 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

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

JavaScript Optimization

-1%

Potential reduce by 792 B

  • Original 109.2 kB
  • After minification 109.2 kB
  • After compression 108.4 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 108 B

  • Original 66.1 kB
  • After minification 66.1 kB
  • After compression 66.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. Web2.dublinairport.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 8 (50%)

Requests Now

16

After Optimization

8

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

web2.dublinairport.com

web2.dublinairport.com

148 ms

web2.dublinairport.com

web2.dublinairport.com

435 ms

gulp_default.min.css

gulp_default.min.css

276 ms

ScriptResource.axd

ScriptResource.axd

404 ms

ScriptResource.axd

ScriptResource.axd

302 ms

ScriptResource.axd

ScriptResource.axd

429 ms

gtm.js

gtm.js

65 ms

Search-box.js

Search-box.js

165 ms

wechat_qr_code.png

wechat_qr_code.png

336 ms

sprite.svg

sprite.svg

99 ms

sprite.css-4a0dc329.svg

sprite.css-4a0dc329.svg

94 ms

app-apple.svg

app-apple.svg

90 ms

app-google-play.svg

app-google-play.svg

92 ms

3040C0_0_0.woff

3040C0_0_0.woff

215 ms

3040C0_1_0.woff

3040C0_1_0.woff

224 ms

otSDKStub.js

otSDKStub.js

104 ms

web.js

web.js

363 ms

4bccac61-d792-4b01-a24c-756d94cbc6bb.json

4bccac61-d792-4b01-a24c-756d94cbc6bb.json

139 ms

location

location

38 ms

otBannerSdk.js

otBannerSdk.js

47 ms

Accessibility Review

web2.dublinairport.com accessibility score

64

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

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[role]s are not contained by their required parent element

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

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

web2.dublinairport.com best practices score

75

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

Browser errors were logged to the console

SEO Factors

web2.dublinairport.com SEO score

92

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

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

web2.dublinairport.com

Open Graph data is detected on the main page of Web 2 Dublin Airport. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: