2.8 sec in total
290 ms
2.3 sec
227 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 290 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
courtgarden.com performance score
name
value
score
weighting
Value10.0 s
0/100
10%
Value15.3 s
0/100
25%
Value12.0 s
4/100
10%
Value1,320 ms
17/100
30%
Value0.021
100/100
15%
Value14.5 s
8/100
10%
290 ms
494 ms
282 ms
270 ms
271 ms
Our browser made a total of 72 requests to load all elements on the main page. We found that 82% of them (59 requests) were addressed to the original Courtgarden.com, 14% (10 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 (991 ms) belongs to the original domain Courtgarden.com.
Page size can be reduced by 105.7 kB (7%)
1.4 MB
1.3 MB
In fact, the total size of Courtgarden.com main page is 1.4 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. 70% of websites need less resources to load. Javascripts take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 102.7 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 102.7 kB or 75% of the original size.
Potential reduce by 0 B
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. Court Garden images are well optimized though.
Potential reduce by 2.3 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 603 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 53 (91%)
58
5
The browser has sent 58 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 54 to 1 for JavaScripts and as a result speed up the page load time.
courtgarden.com
290 ms
courtgarden.com
494 ms
autoptimize_888a25cabcf9849fcd26d7837d2e773c.css
282 ms
wp-polyfill-inert.min.js
270 ms
regenerator-runtime.min.js
271 ms
wp-polyfill.min.js
364 ms
hooks.min.js
276 ms
i18n.min.js
277 ms
css
34 ms
react.min.js
377 ms
react-dom.min.js
546 ms
dom-ready.min.js
378 ms
a11y.min.js
379 ms
deprecated.min.js
378 ms
dom.min.js
457 ms
escape-html.min.js
458 ms
element.min.js
466 ms
is-shallow-equal.min.js
465 ms
keycodes.min.js
466 ms
priority-queue.min.js
553 ms
compose.min.js
552 ms
private-apis.min.js
563 ms
redux-routine.min.js
560 ms
data.min.js
563 ms
html-entities.min.js
636 ms
moment.min.js
643 ms
date.min.js
650 ms
primitives.min.js
655 ms
rich-text.min.js
660 ms
warning.min.js
657 ms
components.min.js
991 ms
jquery.min.js
735 ms
lodash.min.js
741 ms
viewport.min.js
742 ms
horizontal-slim-10_7.css
25 ms
url.min.js
747 ms
api-fetch.min.js
749 ms
blob.min.js
830 ms
autop.min.js
833 ms
block-serialization-default-parser.min.js
832 ms
shortcode.min.js
578 ms
blocks.min.js
667 ms
keyboard-shortcuts.min.js
651 ms
commands.min.js
662 ms
notices.min.js
618 ms
preferences-persistence.min.js
563 ms
preferences.min.js
702 ms
style-engine.min.js
702 ms
token-list.min.js
703 ms
wordcount.min.js
703 ms
block-editor.min.js
671 ms
core-data.min.js
638 ms
media-utils.min.js
643 ms
patterns.min.js
666 ms
server-side-render.min.js
665 ms
editor.min.js
755 ms
data-controls.min.js
634 ms
autoptimize_1bc6137667560e2bebcc97570f54da7d.js
912 ms
cg-sky.png
184 ms
c96b80f31afa5db0fe396c910.js
90 ms
6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7g.ttf
26 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zwlxdr.ttf
33 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwlxdr.ttf
59 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwlxdr.ttf
51 ms
6xKydSBYKcSV-LCoeQqfX1RYOo3iu4nwlxdr.ttf
58 ms
S6uyw4BMUTPHjx4wWw.ttf
56 ms
S6u9w4BMUTPHh6UVSwiPHA.ttf
58 ms
fa-solid-900.woff
251 ms
icomoon.woff
320 ms
wlp_gwjKBV1pqhv43IQ.ttf
56 ms
wlpygwjKBV1pqhND-ZQW-WY.ttf
56 ms
wlpxgwjKBV1pqhv97IMx2Q.ttf
58 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
Browser errors were logged to the console
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
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: