940 ms in total
88 ms
635 ms
217 ms
Welcome to courtgarden.com homepage info - get ready to check Court Garden best content right away, or after learning these important things about courtgarden.com
Award-winning English sparkling wine. Family-run single-estate vineyard and winery in East Sussex; enjoy a vineyard tour with the South Downs as a backdrop.
Visit courtgarden.comWe analyzed Courtgarden.com page load time and found that the first response time was 88 ms and then it took 852 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.
courtgarden.com performance score
name
value
score
weighting
Value3.1 s
46/100
10%
Value11.1 s
0/100
25%
Value6.1 s
44/100
10%
Value990 ms
28/100
30%
Value0.019
100/100
15%
Value10.5 s
24/100
10%
88 ms
54 ms
25 ms
141 ms
88 ms
Our browser made a total of 93 requests to load all elements on the main page. We found that 42% of them (39 requests) were addressed to the original Courtgarden.com, 55% (51 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (374 ms) belongs to the original domain Courtgarden.com.
Page size can be reduced by 60.0 kB (7%)
883.1 kB
823.1 kB
In fact, the total size of Courtgarden.com main page is 883.1 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 614.3 kB which makes up the majority of the site volume.
Potential reduce by 54.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 54.2 kB or 75% of the original size.
Potential reduce by 3.1 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. Obviously, Court Garden needs image optimization as it can save up to 3.1 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 2.0 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.
Potential reduce by 643 B
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. Courtgarden.com has all CSS files already compressed.
Number of requests can be reduced by 34 (89%)
38
4
The browser has sent 38 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Court Garden. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 32 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
courtgarden.com
88 ms
courtgarden.com
54 ms
autoptimize_27c9441bbc4905022dc2c97b63fe6929.css
25 ms
css
141 ms
dashicons.min.css
88 ms
jquery.min.js
88 ms
horizontal-slim-10_7.css
147 ms
lodash.min.js
138 ms
moment.min.js
145 ms
react.min.js
138 ms
hooks.min.js
144 ms
i18n.min.js
144 ms
url.min.js
144 ms
api-fetch.min.js
190 ms
react-dom.min.js
192 ms
react-jsx-runtime.min.js
194 ms
dom-ready.min.js
189 ms
a11y.min.js
192 ms
deprecated.min.js
190 ms
dom.min.js
195 ms
escape-html.min.js
196 ms
element.min.js
203 ms
is-shallow-equal.min.js
202 ms
keycodes.min.js
204 ms
priority-queue.min.js
201 ms
compose.min.js
201 ms
date.min.js
202 ms
html-entities.min.js
214 ms
primitives.min.js
220 ms
private-apis.min.js
374 ms
redux-routine.min.js
214 ms
data.min.js
218 ms
rich-text.min.js
308 ms
warning.min.js
235 ms
components.min.js
305 ms
viewport.min.js
307 ms
autoptimize_3cf6adca8ce088f83bef394e2b04aeab.js
309 ms
cg-sky.png
191 ms
court-garden-script-white.png
369 ms
c96b80f31afa5db0fe396c910.js
152 ms
6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7jujVj9w.woff
49 ms
6xK3dSBYKcSV-LCoeQqfX1RYOo3qNq7jujVj9_mf.woff
55 ms
6xK3dSBYKcSV-LCoeQqfX1RYOo3qN67jujVj9_mf.woff
132 ms
6xK3dSBYKcSV-LCoeQqfX1RYOo3qO67jujVj9_mf.woff
134 ms
6xK3dSBYKcSV-LCoeQqfX1RYOo3qNK7jujVj9_mf.woff
134 ms
6xK3dSBYKcSV-LCoeQqfX1RYOo3qPK7jujVj9_mf.woff
137 ms
6xK3dSBYKcSV-LCoeQqfX1RYOo3qNa7jujVj9_mf.woff
134 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zwlxdo3cOWxw.woff
137 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zwmRdo3cOWxy40.woff
136 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zwmBdo3cOWxy40.woff
139 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zwlBdo3cOWxy40.woff
140 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zwmxdo3cOWxy40.woff
141 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zwkxdo3cOWxy40.woff
140 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zwmhdo3cOWxy40.woff
139 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwlxdo3cOWxw.woff
141 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwmRdo3cOWxy40.woff
199 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwmBdo3cOWxy40.woff
141 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwlBdo3cOWxy40.woff
142 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwmxdo3cOWxy40.woff
142 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwkxdo3cOWxy40.woff
143 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwmhdo3cOWxy40.woff
142 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwlxdo3cOWxw.woff
143 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwmRdo3cOWxy40.woff
144 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwmBdo3cOWxy40.woff
143 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwlBdo3cOWxy40.woff
143 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwmxdo3cOWxy40.woff
144 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwkxdo3cOWxy40.woff
144 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwmhdo3cOWxy40.woff
145 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3iu4nwlxdo3cOWxw.woff
144 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3iu4nwmRdo3cOWxy40.woff
147 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3iu4nwmBdo3cOWxy40.woff
145 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3iu4nwlBdo3cOWxy40.woff
146 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3iu4nwmxdo3cOWxy40.woff
146 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3iu4nwkxdo3cOWxy40.woff
145 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3iu4nwmhdo3cOWxy40.woff
197 ms
S6uyw4BMUTPHjx4wWCWtFCc.woff
50 ms
S6uyw4BMUTPHjxAwWCWtFCfQ7A.woff
48 ms
S6u9w4BMUTPHh6UVSwiPHw3q5d0.woff
49 ms
S6u9w4BMUTPHh6UVSwaPHw3q5d0N7w.woff
48 ms
fa-solid-900.woff
146 ms
icomoon.woff
135 ms
wlp_gwjKBV1pqhv43Ic7225P.woff
49 ms
wlp_gwjKBV1pqhv23Ic7225PUCk.woff
94 ms
wlp_gwjKBV1pqhv73Ic7225PUCk.woff
92 ms
wlp_gwjKBV1pqhv03Ic7225PUCk.woff
93 ms
wlpygwjKBV1pqhND-ZQW-WVlaiBW.woff
94 ms
wlpygwjKBV1pqhND-ZQY-WVlaiBWM_I.woff
95 ms
wlpygwjKBV1pqhND-ZQV-WVlaiBWM_I.woff
92 ms
wlpygwjKBV1pqhND-ZQa-WVlaiBWM_I.woff
114 ms
wlpxgwjKBV1pqhv97IMx2kxNYCg.woff
94 ms
wlpxgwjKBV1pqhv97I0x2kxNYChuCg.woff
114 ms
wlpxgwjKBV1pqhv97IAx2kxNYChuCg.woff
115 ms
wlpxgwjKBV1pqhv97I8x2kxNYChuCg.woff
115 ms
courtgarden.com accessibility score
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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
courtgarden.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
courtgarden.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Page is blocked from indexing
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
Document uses legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Courtgarden.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 Courtgarden.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.
courtgarden.com
Open Graph data is detected on the main page of Court Garden. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: