Tools & Wizards About Us
castlecourt.com screenshot

Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 48% of websites

  • 0

    Best Practices

  • 90

    SEO

    Google-friendlier than
    68% of websites

castlecourt.com

Castle Court School near Wimborne is a leading Dorset Prep School

Page Load Speed

3.4 sec in total

First Response

679 ms

Resources Loaded

2.6 sec

Page Rendered

184 ms

castlecourt.com screenshot

About Website

Welcome to castlecourt.com homepage info - get ready to check Castle Court best content for United Kingdom right away, or after learning these important things about castlecourt.com

A leading Dorset Prep School, based near Wimborne for girls and boys ages 2 - 13. Set in beautiful country grounds with extensive facilities.

Visit castlecourt.com

Key Findings

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

Performance Metrics

castlecourt.com performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

73/100

10%

LCP (Largest Contentful Paint)

Value9.4 s

1/100

25%

SI (Speed Index)

Value4.6 s

70/100

10%

TBT (Total Blocking Time)

Value1,120 ms

23/100

30%

CLS (Cumulative Layout Shift)

Value0.3

39/100

15%

TTI (Time to Interactive)

Value8.5 s

38/100

10%

Network Requests Diagram

www.castlecourt.com

679 ms

reset.css

114 ms

layout.css

193 ms

style.css

207 ms

styles.css

195 ms

Our browser made a total of 53 requests to load all elements on the main page. We found that 94% of them (50 requests) were addressed to the original Castlecourt.com, 4% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Swgflwhisper.org.uk. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Castlecourt.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 277.7 kB (16%)

Content Size

1.8 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-84%

Potential reduce by 37.5 kB

  • Original 44.7 kB
  • After minification 42.2 kB
  • After compression 7.2 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 37.5 kB or 84% of the original size.

Image Optimization

-3%

Potential reduce by 40.9 kB

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

JavaScript Optimization

-64%

Potential reduce by 164.2 kB

  • Original 256.6 kB
  • After minification 251.6 kB
  • After compression 92.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 164.2 kB or 64% of the original size.

CSS Optimization

-84%

Potential reduce by 35.0 kB

  • Original 41.5 kB
  • After minification 28.3 kB
  • After compression 6.6 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. Castlecourt.com needs all CSS files to be minified and compressed as it can save up to 35.0 kB or 84% of the original size.

Requests Breakdown

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

Requests Now

52

After Optimization

22

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.castlecourt.com

www.castlecourt.com

679 ms

reset.css

reset.css

114 ms

layout.css

layout.css

193 ms

style.css

style.css

207 ms

styles.css

styles.css

195 ms

jquery.js

jquery.js

282 ms

jquery-migrate.min.js

jquery-migrate.min.js

189 ms

jquery.cycle.all.min.js

jquery.cycle.all.min.js

231 ms

swfobject.js

swfobject.js

297 ms

core.min.js

core.min.js

277 ms

widget.min.js

widget.min.js

279 ms

tabs.min.js

tabs.min.js

299 ms

apps.js

apps.js

309 ms

jquery.form.min.js

jquery.form.min.js

367 ms

scripts.js

scripts.js

367 ms

wp-embed.min.js

wp-embed.min.js

388 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

207 ms

Green-Example-Button

Green-Example-Button

564 ms

logosmall.png

logosmall.png

201 ms

box-bg.png

box-bg.png

188 ms

box-tl.png

box-tl.png

190 ms

box-tr.png

box-tr.png

188 ms

box-bl.png

box-bl.png

189 ms

box-br.png

box-br.png

190 ms

box-t.png

box-t.png

189 ms

box-r.png

box-r.png

245 ms

box-b.png

box-b.png

244 ms

box-l.png

box-l.png

252 ms

nav-arrow-right.png

nav-arrow-right.png

263 ms

nav-button-up-l.png

nav-button-up-l.png

267 ms

nav-button-up-r.png

nav-button-up-r.png

293 ms

main-image.jpg

main-image.jpg

805 ms

main-image1.jpg

main-image1.jpg

808 ms

main-image3.jpg

main-image3.jpg

659 ms

main-image4.jpg

main-image4.jpg

843 ms

main-image5.jpg

main-image5.jpg

899 ms

sprite_buttons.png

sprite_buttons.png

508 ms

sprite_corners.png

sprite_corners.png

603 ms

ico-feed.png

ico-feed.png

722 ms

P1020764-122x91.jpg

P1020764-122x91.jpg

765 ms

Sports_Hall_rendersDraft-9-Feb1-3wm-122x91.jpg

Sports_Hall_rendersDraft-9-Feb1-3wm-122x91.jpg

835 ms

castle-court.png

castle-court.png

872 ms

arch-small-22.png

arch-small-22.png

903 ms

gallery.png

gallery.png

914 ms

parent.png

parent.png

1020 ms

the-good-schools-guide.jpg

the-good-schools-guide.jpg

936 ms

button-isi-logo.png

button-isi-logo.png

966 ms

facebook.png

facebook.png

991 ms

youtube.png

youtube.png

993 ms

ga.js

ga.js

24 ms

instagram.png

instagram.png

990 ms

horizontal-line-shadow.png

horizontal-line-shadow.png

992 ms

__utm.gif

__utm.gif

125 ms

Accessibility Review

castlecourt.com accessibility score

79

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-*] attributes do not match their roles

High

ARIA input fields do not have accessible names

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

Form elements do not have associated labels

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.

SEO Factors

castlecourt.com SEO score

90

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

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Castlecourt.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Castlecourt.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

castlecourt.com

Open Graph description is not detected on the main page of Castle Court. 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: