Tools & Wizards About Us
invercauld.estate screenshot

Report Summary

  • 13

    Performance

    Renders faster than
    25% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 87% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

invercauld.estate

Welcome to Invercauld Estate

Page Load Speed

5.7 sec in total

First Response

419 ms

Resources Loaded

4.9 sec

Page Rendered

459 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 419 ms and then it took 5.3 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

invercauld.estate performance score

13

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.9 s

0/100

10%

LCP (Largest Contentful Paint)

Value16.0 s

0/100

25%

SI (Speed Index)

Value16.1 s

0/100

10%

TBT (Total Blocking Time)

Value1,680 ms

11/100

30%

CLS (Cumulative Layout Shift)

Value0.202

61/100

15%

TTI (Time to Interactive)

Value16.8 s

5/100

10%

Network Requests Diagram

www.invercauld.estate

419 ms

fadc052996c71cbcdfba92fb7c2e9887.css

341 ms

uc.js

21 ms

wp-polyfill-inert.min.js

187 ms

regenerator-runtime.min.js

236 ms

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

Page Optimization Overview & Recommendations

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

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. 65% of websites need less resources to load. Images take 980.2 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 106.8 kB

  • Original 133.1 kB
  • After minification 127.0 kB
  • After compression 26.4 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 106.8 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

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

JavaScript Optimization

-15%

Potential reduce by 99.0 kB

  • Original 654.1 kB
  • After minification 654.1 kB
  • After compression 555.1 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 99.0 kB or 15% of the original size.

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 148.0 kB
  • After minification 148.0 kB
  • After compression 148.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 66 (73%)

Requests Now

91

After Optimization

25

  • Images
  • JavaScript
  • CSS

The browser has sent 91 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 67 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

www.invercauld.estate

www.invercauld.estate

419 ms

fadc052996c71cbcdfba92fb7c2e9887.css

fadc052996c71cbcdfba92fb7c2e9887.css

341 ms

uc.js

uc.js

21 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

187 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

236 ms

wp-polyfill.min.js

wp-polyfill.min.js

330 ms

hooks.min.js

hooks.min.js

252 ms

w.js

w.js

17 ms

wpi_script.js

wpi_script.js

255 ms

jquery.min.js

jquery.min.js

356 ms

jquery-migrate.min.js

jquery-migrate.min.js

313 ms

snazzymaps.js

snazzymaps.js

344 ms

sow.google-map.min.js

sow.google-map.min.js

344 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

345 ms

add-to-cart.min.js

add-to-cart.min.js

419 ms

js.cookie.min.js

js.cookie.min.js

418 ms

woocommerce.min.js

woocommerce.min.js

421 ms

front_global.js

front_global.js

423 ms

front_script.js

front_script.js

425 ms

js

js

70 ms

imagesloaded.js

imagesloaded.js

452 ms

rbtools.min.js

rbtools.min.js

655 ms

rs6.min.js

rs6.min.js

675 ms

touchy.js

touchy.js

535 ms

sourcebuster.min.js

sourcebuster.min.js

536 ms

order-attribution.min.js

order-attribution.min.js

535 ms

react.min.js

react.min.js

545 ms

deprecated.min.js

deprecated.min.js

597 ms

dom.min.js

dom.min.js

598 ms

react-dom.min.js

react-dom.min.js

682 ms

escape-html.min.js

escape-html.min.js

619 ms

element.min.js

element.min.js

673 ms

is-shallow-equal.min.js

is-shallow-equal.min.js

680 ms

i18n.min.js

i18n.min.js

702 ms

keycodes.min.js

keycodes.min.js

733 ms

priority-queue.min.js

priority-queue.min.js

757 ms

compose.min.js

compose.min.js

757 ms

private-apis.min.js

private-apis.min.js

769 ms

redux-routine.min.js

redux-routine.min.js

776 ms

data.min.js

data.min.js

785 ms

lodash.min.js

lodash.min.js

634 ms

wc-blocks-registry.js

wc-blocks-registry.js

619 ms

url.min.js

url.min.js

598 ms

api-fetch.min.js

api-fetch.min.js

602 ms

wc-settings.js

wc-settings.js

557 ms

data-controls.min.js

data-controls.min.js

561 ms

g.gif

g.gif

27 ms

html-entities.min.js

html-entities.min.js

556 ms

notices.min.js

notices.min.js

586 ms

wc-blocks-middleware.js

wc-blocks-middleware.js

590 ms

wc-blocks-data.js

wc-blocks-data.js

593 ms

dom-ready.min.js

dom-ready.min.js

581 ms

a11y.min.js

a11y.min.js

538 ms

primitives.min.js

primitives.min.js

558 ms

warning.min.js

warning.min.js

589 ms

blocks-components.js

blocks-components.js

675 ms

blocks-checkout.js

blocks-checkout.js

572 ms

order-attribution-blocks.min.js

order-attribution-blocks.min.js

530 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

42 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

43 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

72 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

80 ms

esDR31xSG-6AGleN2tWklQ.ttf

esDR31xSG-6AGleN2tWklQ.ttf

78 ms

wow.min.js

wow.min.js

501 ms

jquery.background-video.js

jquery.background-video.js

518 ms

jquery.actual.js

jquery.actual.js

552 ms

superfish.js

superfish.js

559 ms

jquery.waitforimages.min.js

jquery.waitforimages.min.js

513 ms

owl.carousel.min.js

owl.carousel.min.js

521 ms

jquery.isotope.js

jquery.isotope.js

525 ms

jquery.fitvids.js

jquery.fitvids.js

533 ms

jquery.scrollTo.js

jquery.scrollTo.js

534 ms

jquery.prettyPhoto.js

jquery.prettyPhoto.js

532 ms

theme_trust.js

theme_trust.js

534 ms

styling.min.js

styling.min.js

525 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

630 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

563 ms

fa-v4compatibility.ttf

fa-v4compatibility.ttf

540 ms

fa-regular-400.ttf

fa-regular-400.ttf

539 ms

fa-brands-400.ttf

fa-brands-400.ttf

771 ms

fa-solid-900.ttf

fa-solid-900.ttf

772 ms

inverclaud-logo-blue-s.png

inverclaud-logo-blue-s.png

583 ms

dummy.png

dummy.png

550 ms

home-holding.-768x475.jpg

home-holding.-768x475.jpg

530 ms

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

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

612 ms

font-working-landscape-768x484.jpg

font-working-landscape-768x484.jpg

601 ms

font-lettings-768x484.jpg

font-lettings-768x484.jpg

676 ms

front-activities-768x614.jpg

front-activities-768x614.jpg

586 ms

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

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

643 ms

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

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

614 ms

IMG_4608-800x600.jpg

IMG_4608-800x600.jpg

687 ms

New-Payment-Meter.jpg

New-Payment-Meter.jpg

764 ms

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

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

674 ms

IMG_3793-800x600.jpg

IMG_3793-800x600.jpg

668 ms

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

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

654 ms

Heather-Burning-Gairnshiel-Feb-2023-Cropped-800x600.jpg

Heather-Burning-Gairnshiel-Feb-2023-Cropped-800x600.jpg

620 ms

invercauld-logo-sq-800x600.jpg

invercauld-logo-sq-800x600.jpg

678 ms

Caper-marking-2022-2-Ian-Hill-Cropped-3-2.jpg

Caper-marking-2022-2-Ian-Hill-Cropped-3-2.jpg

673 ms

sea-eagle-news-800x600.jpg

sea-eagle-news-800x600.jpg

667 ms

Cairn-and-Foghouse-fro-South-adjusted-2-800x600.jpg

Cairn-and-Foghouse-fro-South-adjusted-2-800x600.jpg

658 ms

Screenshot-2022-10-25-at-11.50.15-800x600.jpg

Screenshot-2022-10-25-at-11.50.15-800x600.jpg

624 ms

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

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

673 ms

lines.gif

lines.gif

755 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: