Tools & Wizards About Us

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 67

    Accessibility

    Visual factors better than
    that of 32% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 71

    SEO

    Google-friendlier than
    30% of websites

courtyard.ie

Court Yard Hotel I Charming Hotel Accommodation in Leixlip

Page Load Speed

7.7 sec in total

First Response

291 ms

Resources Loaded

6.9 sec

Page Rendered

559 ms

About Website

Welcome to courtyard.ie homepage info - get ready to check Court Yard best content right away, or after learning these important things about courtyard.ie

The official website of the Court Yard Hotel. This Leixlip hotel is located in the heart of the picturesque village of Leixlip, Co. Kildare

Visit courtyard.ie

Key Findings

We analyzed Courtyard.ie page load time and found that the first response time was 291 ms and then it took 7.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

courtyard.ie performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.3 s

1/100

10%

LCP (Largest Contentful Paint)

Value7.6 s

4/100

25%

SI (Speed Index)

Value12.6 s

3/100

10%

TBT (Total Blocking Time)

Value2,220 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.115

86/100

15%

TTI (Time to Interactive)

Value27.5 s

0/100

10%

Network Requests Diagram

courtyard.ie

291 ms

www.courtyard.ie

2418 ms

main.css

134 ms

jquery.bxslider.css

203 ms

styles.css

277 ms

Our browser made a total of 151 requests to load all elements on the main page. We found that 77% of them (117 requests) were addressed to the original Courtyard.ie, 5% (8 requests) were made to Fonts.gstatic.com and 3% (5 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Courtyard.ie.

Page Optimization Overview & Recommendations

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

Content Size

2.9 MB

After Optimization

2.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Courtyard.ie main page is 2.9 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. Only a small number of websites need less resources to load. Images take 2.3 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 119.4 kB

  • Original 137.3 kB
  • After minification 125.8 kB
  • After compression 17.8 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 119.4 kB or 87% of the original size.

Image Optimization

-2%

Potential reduce by 48.4 kB

  • Original 2.3 MB
  • After minification 2.2 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. Court Yard images are well optimized though.

JavaScript Optimization

-27%

Potential reduce by 120.8 kB

  • Original 440.4 kB
  • After minification 440.4 kB
  • After compression 319.7 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 120.8 kB or 27% of the original size.

CSS Optimization

-26%

Potential reduce by 30.0 kB

  • Original 115.9 kB
  • After minification 113.3 kB
  • After compression 85.9 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. Courtyard.ie needs all CSS files to be minified and compressed as it can save up to 30.0 kB or 26% of the original size.

Requests Breakdown

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

Requests Now

139

After Optimization

100

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

courtyard.ie accessibility score

67

Accessibility Issues

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.

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

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

courtyard.ie best practices score

67

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

courtyard.ie SEO score

71

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

Links do not have descriptive text

High

Image elements do not have [alt] attributes

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

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 Courtyard.ie 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 Courtyard.ie 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 Court Yard. 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: