Tools & Wizards About Us
whittlebury.com screenshot

Report Summary

  • 48

    Performance

    Renders faster than
    66% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

whittlebury.com

Whittlebury Park | Conference Centre, 4* Hotel & Spa

Page Load Speed

4.2 sec in total

First Response

161 ms

Resources Loaded

3.9 sec

Page Rendered

192 ms

whittlebury.com screenshot

About Website

Visit whittlebury.com now to see the best up-to-date Whittlebury content and also check out these interesting facts you probably never knew about whittlebury.com

We're waiting to extend a warm welcome to you, whether you're at Whittlebury Park for a conference, spa break, golfing weekend or wedding.

Visit whittlebury.com

Key Findings

We analyzed Whittlebury.com page load time and found that the first response time was 161 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

whittlebury.com performance score

48

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

65/100

10%

LCP (Largest Contentful Paint)

Value8.3 s

2/100

25%

SI (Speed Index)

Value4.6 s

70/100

10%

TBT (Total Blocking Time)

Value120 ms

97/100

30%

CLS (Cumulative Layout Shift)

Value0.839

4/100

15%

TTI (Time to Interactive)

Value7.7 s

46/100

10%

Network Requests Diagram

whittlebury.com

161 ms

www.whittlebury.com

2699 ms

jquery.min.js

8 ms

FA01D5618ACFBDC9E04821A0DF757366_12F2F205.js

180 ms

lazysizes.min.js

159 ms

Our browser made a total of 37 requests to load all elements on the main page. We found that 97% of them (36 requests) were addressed to the original Whittlebury.com, 3% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain Whittlebury.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 188.2 kB (21%)

Content Size

911.0 kB

After Optimization

722.8 kB

  • HTML
  • Images
  • JavaScript

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

HTML Optimization

-84%

Potential reduce by 115.4 kB

  • Original 137.5 kB
  • After minification 116.6 kB
  • After compression 22.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. This page needs HTML code to be minified as it can gain 20.9 kB, which is 15% 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 115.4 kB or 84% of the original size.

Image Optimization

-5%

Potential reduce by 35.2 kB

  • Original 640.7 kB
  • After minification 605.5 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. Whittlebury images are well optimized though.

JavaScript Optimization

-28%

Potential reduce by 37.6 kB

  • Original 132.8 kB
  • After minification 132.8 kB
  • After compression 95.2 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 37.6 kB or 28% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

28

After Optimization

28

  • AJAX
  • Images
  • JavaScript

The browser has sent 28 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Whittlebury. According to our analytics all requests are already optimized.

Network Requests Diagram

whittlebury.com

whittlebury.com

161 ms

www.whittlebury.com

www.whittlebury.com

2699 ms

jquery.min.js

jquery.min.js

8 ms

FA01D5618ACFBDC9E04821A0DF757366_12F2F205.js

FA01D5618ACFBDC9E04821A0DF757366_12F2F205.js

180 ms

lazysizes.min.js

lazysizes.min.js

159 ms

WHlogo_light.png

WHlogo_light.png

237 ms

loading.gif

loading.gif

235 ms

navRight.png

navRight.png

235 ms

navLeft.png

navLeft.png

235 ms

inc-mega-menu.cfm

inc-mega-menu.cfm

597 ms

loading_background.png

loading_background.png

82 ms

loading.gif

loading.gif

83 ms

controls.png

controls.png

81 ms

btn_close.png

btn_close.png

85 ms

www.whittlebury.com

www.whittlebury.com

618 ms

Bliss2R.svg

Bliss2R.svg

316 ms

daxm77-webfont.svg

daxm77-webfont.svg

239 ms

Bliss2L.svg

Bliss2L.svg

324 ms

daxr42-webfont.svg

daxr42-webfont.svg

247 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

400 ms

Bliss2B.svg

Bliss2B.svg

410 ms

daxeb15-webfont.svg

daxeb15-webfont.svg

396 ms

slide315-4.jpg

slide315-4.jpg

458 ms

slide313-55.jpg

slide313-55.jpg

527 ms

footerLogo22.png

footerLogo22.png

331 ms

footerLogo03.png

footerLogo03.png

411 ms

footerLogo05.png

footerLogo05.png

412 ms

footerLogo07.png

footerLogo07.png

422 ms

footerLogo08.png

footerLogo08.png

488 ms

footerLogo09.png

footerLogo09.png

492 ms

footerLogo20.jpg

footerLogo20.jpg

490 ms

daxm77-webfont.woff

daxm77-webfont.woff

405 ms

daxr42-webfont.woff

daxr42-webfont.woff

417 ms

Bliss2R.woff

Bliss2R.woff

374 ms

Bliss2L.woff

Bliss2L.woff

384 ms

daxeb15-webfont.woff

daxeb15-webfont.woff

309 ms

Bliss2B.woff

Bliss2B.woff

313 ms

Accessibility Review

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

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

whittlebury.com SEO score

92

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

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

whittlebury.com

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