Tools & Wizards About Us
invercauld.estate screenshot

Report Summary

  • 11

    Performance

    Renders faster than
    24% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

invercauld.estate

Welcome to Invercauld Estate

Page Load Speed

5.3 sec in total

First Response

490 ms

Resources Loaded

4.3 sec

Page Rendered

591 ms

invercauld.estate screenshot

About Website

Click here to check amazing Invercauld content. Otherwise, check out these important facts you probably never knew about invercauld.estate

Located near Braemar on Royal Deeside, Aberdeenshire, Invercauld Estate covers approximately 95,000 acres of the Cairngorms National Park.

Visit invercauld.estate

Key Findings

We analyzed Invercauld.estate page load time and found that the first response time was 490 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

invercauld.estate performance score

11

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.5 s

0/100

10%

LCP (Largest Contentful Paint)

Value15.9 s

0/100

25%

SI (Speed Index)

Value18.7 s

0/100

10%

TBT (Total Blocking Time)

Value2,560 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.202

61/100

15%

TTI (Time to Interactive)

Value17.5 s

4/100

10%

Network Requests Diagram

www.invercauld.estate

490 ms

bf82dc3fcf412744d9861774f6e546ba.css

332 ms

uc.js

26 ms

wpi_script.js

158 ms

jquery.min.js

322 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 89% of them (59 requests) were addressed to the original Invercauld.estate, 8% (5 requests) were made to Fonts.gstatic.com and 2% (1 request) were made to Consent.cookiebot.com. The less responsive or slowest element that took the longest time to load (752 ms) belongs to the original domain Invercauld.estate.

Page Optimization Overview & Recommendations

Page size can be reduced by 189.8 kB (10%)

Content Size

1.9 MB

After Optimization

1.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Invercauld.estate main page is 1.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 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 91.0 kB

  • Original 111.8 kB
  • After minification 105.8 kB
  • After compression 20.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 91.0 kB or 81% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 1.3 MB
  • After minification 1.3 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. Invercauld images are well optimized though.

JavaScript Optimization

-25%

Potential reduce by 98.8 kB

  • Original 391.3 kB
  • After minification 391.2 kB
  • After compression 292.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 98.8 kB or 25% of the original size.

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 149.0 kB
  • After minification 149.0 kB
  • After compression 149.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. Invercauld.estate has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 30 (56%)

Requests Now

54

After Optimization

24

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.invercauld.estate

www.invercauld.estate

490 ms

bf82dc3fcf412744d9861774f6e546ba.css

bf82dc3fcf412744d9861774f6e546ba.css

332 ms

uc.js

uc.js

26 ms

wpi_script.js

wpi_script.js

158 ms

jquery.min.js

jquery.min.js

322 ms

jquery-migrate.min.js

jquery-migrate.min.js

246 ms

snazzymaps.js

snazzymaps.js

245 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

248 ms

add-to-cart.min.js

add-to-cart.min.js

247 ms

js.cookie.min.js

js.cookie.min.js

333 ms

woocommerce.min.js

woocommerce.min.js

333 ms

front_global.js

front_global.js

333 ms

front_script.js

front_script.js

334 ms

imagesloaded.js

imagesloaded.js

335 ms

js

js

83 ms

rbtools.min.js

rbtools.min.js

491 ms

rs6.min.js

rs6.min.js

679 ms

touchy.js

touchy.js

450 ms

wow.min.js

wow.min.js

450 ms

jquery.background-video.js

jquery.background-video.js

451 ms

sourcebuster.min.js

sourcebuster.min.js

451 ms

order-attribution.min.js

order-attribution.min.js

522 ms

jquery.actual.js

jquery.actual.js

524 ms

superfish.js

superfish.js

524 ms

jquery.waitforimages.min.js

jquery.waitforimages.min.js

523 ms

owl.carousel.min.js

owl.carousel.min.js

571 ms

jquery.isotope.js

jquery.isotope.js

605 ms

jquery.fitvids.js

jquery.fitvids.js

611 ms

jquery.scrollTo.js

jquery.scrollTo.js

611 ms

jquery.prettyPhoto.js

jquery.prettyPhoto.js

609 ms

theme_trust.js

theme_trust.js

650 ms

styling.min.js

styling.min.js

684 ms

sow.google-map.min.js

sow.google-map.min.js

688 ms

inverclaud-logo-blue-s.png

inverclaud-logo-blue-s.png

369 ms

dummy.png

dummy.png

367 ms

home-holding.-768x475.jpg

home-holding.-768x475.jpg

470 ms

front-envoronment-and-people-768x614.jpg

front-envoronment-and-people-768x614.jpg

496 ms

font-working-landscape-768x484.jpg

font-working-landscape-768x484.jpg

427 ms

font-lettings-768x484.jpg

font-lettings-768x484.jpg

587 ms

front-activities-768x614.jpg

front-activities-768x614.jpg

588 ms

The-Old-Brig-o-Dee-768x576.jpg

The-Old-Brig-o-Dee-768x576.jpg

588 ms

DJI_0280-800x600.jpg

DJI_0280-800x600.jpg

506 ms

DJI_0754Adjust-800x600.jpg

DJI_0754Adjust-800x600.jpg

636 ms

Waymarking-post.jpg

Waymarking-post.jpg

575 ms

iStock-139531068-Mayfly-800x600.jpg

iStock-139531068-Mayfly-800x600.jpg

584 ms

Willie-Wildcat-800x600.jpg

Willie-Wildcat-800x600.jpg

658 ms

Steve-Denham-Dyking-April-2024-800x600.jpg

Steve-Denham-Dyking-April-2024-800x600.jpg

745 ms

Landward-Boardcast-Card-Nov-2023-800x600.jpg

Landward-Boardcast-Card-Nov-2023-800x600.jpg

745 ms

IMG_4608-800x600.jpg

IMG_4608-800x600.jpg

752 ms

New-Payment-Meter.jpg

New-Payment-Meter.jpg

752 ms

Geroge-Duff-Shoot-Car-Parking-June-2023-e1686741981266.jpg

Geroge-Duff-Shoot-Car-Parking-June-2023-e1686741981266.jpg

670 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

42 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

42 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

63 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

79 ms

esDR31xSG-6AGleN2tWklQ.ttf

esDR31xSG-6AGleN2tWklQ.ttf

80 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

626 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

684 ms

fa-v4compatibility.ttf

fa-v4compatibility.ttf

705 ms

fa-regular-400.ttf

fa-regular-400.ttf

700 ms

fa-brands-400.ttf

fa-brands-400.ttf

728 ms

fa-solid-900.ttf

fa-solid-900.ttf

721 ms

IMG_3793-800x600.jpg

IMG_3793-800x600.jpg

653 ms

Station-Square-Sign-Ballater-RD-Ltd-2-800x600.jpg

Station-Square-Sign-Ballater-RD-Ltd-2-800x600.jpg

690 ms

150x88xcairngorms-np-logo-white-footer.png.pagespeed.ic_.dlF-olzm21.png

150x88xcairngorms-np-logo-white-footer.png.pagespeed.ic_.dlF-olzm21.png

709 ms

lines.gif

lines.gif

664 ms

Accessibility Review

invercauld.estate accessibility score

95

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

Links do not have a discernible name

Best Practices

invercauld.estate 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

invercauld.estate 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 Invercauld.estate 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 Invercauld.estate 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

invercauld.estate

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