Tools & Wizards About Us
irondonkey.com screenshot

Report Summary

  • 48

    Performance

    Renders faster than
    66% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

irondonkey.com

Iron Donkey Cycle Tours | Ireland, Great Britain, Spain & Italy

Page Load Speed

5.3 sec in total

First Response

206 ms

Resources Loaded

3.1 sec

Page Rendered

2 sec

irondonkey.com screenshot

About Website

Visit irondonkey.com now to see the best up-to-date Iron Donkey content for Canada and also check out these interesting facts you probably never knew about irondonkey.com

Cycling Holidays & Tours in Ireland, Great Britain, Italy and Spain. Guided & self-guided tours. Tried and tested tours designed by cyclists.

Visit irondonkey.com

Key Findings

We analyzed Irondonkey.com page load time and found that the first response time was 206 ms and then it took 5.1 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

irondonkey.com performance score

48

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

85/100

10%

LCP (Largest Contentful Paint)

Value107.5 s

0/100

25%

SI (Speed Index)

Value6.0 s

47/100

10%

TBT (Total Blocking Time)

Value470 ms

61/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value12.0 s

16/100

10%

Network Requests Diagram

irondonkey.com

206 ms

irondonkey.com

984 ms

app.css

158 ms

api.js

29 ms

app.js

458 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 55% of them (31 requests) were addressed to the original Irondonkey.com, 34% (19 requests) were made to S3.eu-west-1.amazonaws.com and 4% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source S3.eu-west-1.amazonaws.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 3.7 MB (9%)

Content Size

39.9 MB

After Optimization

36.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Irondonkey.com main page is 39.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. 55% of websites need less resources to load. Images take 39.5 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 48.9 kB

  • Original 61.0 kB
  • After minification 57.6 kB
  • After compression 12.1 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 48.9 kB or 80% of the original size.

Image Optimization

-9%

Potential reduce by 3.6 MB

  • Original 39.5 MB
  • After minification 35.8 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. Iron Donkey images are well optimized though.

JavaScript Optimization

-6%

Potential reduce by 20.2 kB

  • Original 365.5 kB
  • After minification 365.5 kB
  • After compression 345.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

-22%

Potential reduce by 5.6 kB

  • Original 25.7 kB
  • After minification 25.7 kB
  • After compression 20.1 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. Irondonkey.com needs all CSS files to be minified and compressed as it can save up to 5.6 kB or 22% of the original size.

Requests Breakdown

Number of requests can be reduced by 5 (10%)

Requests Now

51

After Optimization

46

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

irondonkey.com

irondonkey.com

206 ms

irondonkey.com

irondonkey.com

984 ms

app.css

app.css

158 ms

api.js

api.js

29 ms

app.js

app.js

458 ms

recaptcha__en.js

recaptcha__en.js

24 ms

gtm.js

gtm.js

73 ms

analytics.js

analytics.js

28 ms

usp-map-marker.svg

usp-map-marker.svg

396 ms

logo.svg

logo.svg

96 ms

magnify-blue.svg

magnify-blue.svg

196 ms

hamburger-grey.svg

hamburger-grey.svg

244 ms

magnify-grey.svg

magnify-grey.svg

379 ms

camera-white.svg

camera-white.svg

381 ms

image-card-holder.png

image-card-holder.png

381 ms

star-rating.svg

star-rating.svg

379 ms

newsletter-bg.jpg

newsletter-bg.jpg

466 ms

logo-white.svg

logo-white.svg

385 ms

usp-clock.svg

usp-clock.svg

382 ms

usp-person.svg

usp-person.svg

384 ms

usp-tick.svg

usp-tick.svg

383 ms

Tuscan-Hills.jpg

Tuscan-Hills.jpg

1410 ms

Ireland-Homepage.png

Ireland-Homepage.png

794 ms

Great-Britain-Homepage.png

Great-Britain-Homepage.png

920 ms

Italy-Homepage.png

Italy-Homepage.png

868 ms

Spain-Homepage.png

Spain-Homepage.png

886 ms

social-facebook-white.svg

social-facebook-white.svg

448 ms

social-twitter-white.svg

social-twitter-white.svg

568 ms

Rubik-Regular.woff

Rubik-Regular.woff

508 ms

collect

collect

38 ms

Rubik-Medium.woff

Rubik-Medium.woff

458 ms

Rubik-Bold.woff

Rubik-Bold.woff

458 ms

js

js

52 ms

world-blue.svg

world-blue.svg

79 ms

map-marker-blue.svg

map-marker-blue.svg

78 ms

compass-blue.svg

compass-blue.svg

150 ms

calendar-blue.svg

calendar-blue.svg

152 ms

4068

4068

452 ms

8182

8182

991 ms

9373

9373

660 ms

11145

11145

890 ms

6144

6144

777 ms

8298

8298

553 ms

9495

9495

1125 ms

11285

11285

1224 ms

bespoke-card.jpg

bespoke-card.jpg

878 ms

fav.svg

fav.svg

846 ms

add-white.svg

add-white.svg

470 ms

Kilkee-2.jpg

Kilkee-2.jpg

346 ms

imgonline-com-ua-resize-OTb4nu6aEqFbHmd.jpg

imgonline-com-ua-resize-OTb4nu6aEqFbHmd.jpg

94 ms

imgonline-com-ua-resize-u5ocIZaXGdsyu.jpg

imgonline-com-ua-resize-u5ocIZaXGdsyu.jpg

119 ms

Burren.jpg

Burren.jpg

582 ms

imgonline-com-ua-resize-pfhb37nj8sIE.jpg

imgonline-com-ua-resize-pfhb37nj8sIE.jpg

139 ms

imgonline-com-ua-resize-UCNQ2AhGbduR.jpg

imgonline-com-ua-resize-UCNQ2AhGbduR.jpg

92 ms

imgonline-com-ua-resize-hVVQlocjgonooGdF.jpg

imgonline-com-ua-resize-hVVQlocjgonooGdF.jpg

130 ms

imgonline-com-ua-resize-ZpRtxp1flnSi4yUL.jpg

imgonline-com-ua-resize-ZpRtxp1flnSi4yUL.jpg

91 ms

Accessibility Review

irondonkey.com accessibility score

66

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

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

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

irondonkey.com 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

irondonkey.com SEO score

93

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

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

irondonkey.com

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