Tools & Wizards About Us
saffrongrange.com screenshot

Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

saffrongrange.com

English Sparkling wine - Saffron Grange Vineyard

Page Load Speed

2.6 sec in total

First Response

284 ms

Resources Loaded

2 sec

Page Rendered

372 ms

saffrongrange.com screenshot

About Website

Click here to check amazing Saffron Grange content. Otherwise, check out these important facts you probably never knew about saffrongrange.com

Discover the finest English Sparkling wine at Saffron Grange, a family-run vineyard near the historic market town of Saffron Walden.

Visit saffrongrange.com

Key Findings

We analyzed Saffrongrange.com page load time and found that the first response time was 284 ms and then it took 2.3 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.

Performance Metrics

saffrongrange.com performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.6 s

2/100

10%

LCP (Largest Contentful Paint)

Value9.5 s

0/100

25%

SI (Speed Index)

Value9.5 s

12/100

10%

TBT (Total Blocking Time)

Value650 ms

46/100

30%

CLS (Cumulative Layout Shift)

Value0.047

99/100

15%

TTI (Time to Interactive)

Value11.4 s

19/100

10%

Network Requests Diagram

saffrongrange.com

284 ms

www.saffrongrange.com

233 ms

style.min.css

216 ms

main.css

266 ms

woocommerce-layout.css

187 ms

Our browser made a total of 93 requests to load all elements on the main page. We found that 83% of them (77 requests) were addressed to the original Saffrongrange.com, 8% (7 requests) were made to Use.typekit.net and 3% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (696 ms) belongs to the original domain Saffrongrange.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 58.1 kB (14%)

Content Size

423.5 kB

After Optimization

365.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Saffrongrange.com main page is 423.5 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. 75% 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. Images take 322.7 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 58.0 kB

  • Original 74.9 kB
  • After minification 71.6 kB
  • After compression 16.9 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 58.0 kB or 77% of the original size.

Image Optimization

-0%

Potential reduce by 42 B

  • Original 322.7 kB
  • After minification 322.7 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. Saffron Grange images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 77 B

  • Original 25.9 kB
  • After minification 25.9 kB
  • After compression 25.8 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.

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 5 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.

Requests Breakdown

Number of requests can be reduced by 68 (85%)

Requests Now

80

After Optimization

12

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

saffrongrange.com

saffrongrange.com

284 ms

www.saffrongrange.com

www.saffrongrange.com

233 ms

style.min.css

style.min.css

216 ms

main.css

main.css

266 ms

woocommerce-layout.css

woocommerce-layout.css

187 ms

woocommerce.css

woocommerce.css

276 ms

front.min.css

front.min.css

262 ms

xoo-cp-style.css

xoo-cp-style.css

85 ms

jquery-ui-styles.css

jquery-ui-styles.css

132 ms

frontend.css

frontend.css

156 ms

styles.css

styles.css

197 ms

front.min.css

front.min.css

220 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

223 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

291 ms

wp-polyfill.min.js

wp-polyfill.min.js

347 ms

hooks.min.js

hooks.min.js

251 ms

w.js

w.js

22 ms

jquery.min.js

jquery.min.js

292 ms

jquery-migrate.min.js

jquery-migrate.min.js

302 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

300 ms

add-to-cart.min.js

add-to-cart.min.js

308 ms

js.cookie.min.js

js.cookie.min.js

335 ms

woocommerce.min.js

woocommerce.min.js

316 ms

cart-fragments.min.js

cart-fragments.min.js

346 ms

wc-blocks.css

wc-blocks.css

337 ms

focus.js

focus.js

331 ms

all.js

all.js

345 ms

sourcebuster.min.js

sourcebuster.min.js

470 ms

order-attribution.min.js

order-attribution.min.js

360 ms

react.min.js

react.min.js

473 ms

deprecated.min.js

deprecated.min.js

471 ms

dom.min.js

dom.min.js

383 ms

react-dom.min.js

react-dom.min.js

367 ms

escape-html.min.js

escape-html.min.js

480 ms

element.min.js

element.min.js

471 ms

is-shallow-equal.min.js

is-shallow-equal.min.js

481 ms

i18n.min.js

i18n.min.js

486 ms

keycodes.min.js

keycodes.min.js

487 ms

priority-queue.min.js

priority-queue.min.js

467 ms

compose.min.js

compose.min.js

410 ms

private-apis.min.js

private-apis.min.js

363 ms

redux-routine.min.js

redux-routine.min.js

338 ms

data.min.js

data.min.js

310 ms

nxq4nes.css

nxq4nes.css

164 ms

lodash.min.js

lodash.min.js

324 ms

wc-blocks-registry.js

wc-blocks-registry.js

307 ms

url.min.js

url.min.js

335 ms

api-fetch.min.js

api-fetch.min.js

331 ms

wc-settings.js

wc-settings.js

308 ms

data-controls.min.js

data-controls.min.js

275 ms

html-entities.min.js

html-entities.min.js

286 ms

notices.min.js

notices.min.js

283 ms

wc-blocks-middleware.js

wc-blocks-middleware.js

273 ms

wc-blocks-data.js

wc-blocks-data.js

326 ms

dom-ready.min.js

dom-ready.min.js

292 ms

a11y.min.js

a11y.min.js

291 ms

primitives.min.js

primitives.min.js

302 ms

warning.min.js

warning.min.js

276 ms

blocks-components.js

blocks-components.js

276 ms

blocks-checkout.js

blocks-checkout.js

275 ms

order-attribution-blocks.min.js

order-attribution-blocks.min.js

273 ms

xoo-cp-js.js

xoo-cp-js.js

311 ms

globals.js

globals.js

303 ms

front.min.js

front.min.js

351 ms

p.css

p.css

32 ms

age-gate.js

age-gate.js

294 ms

smush-lazy-load.min.js

smush-lazy-load.min.js

280 ms

g.gif

g.gif

82 ms

gtm.js

gtm.js

144 ms

home-hero-1400x600.jpg

home-hero-1400x600.jpg

264 ms

home-bottle-close.jpg

home-bottle-close.jpg

353 ms

home-story.jpg

home-story.jpg

224 ms

d

d

13 ms

d

d

30 ms

d

d

34 ms

d

d

34 ms

d

d

46 ms

d

d

46 ms

fa-solid-900.woff

fa-solid-900.woff

268 ms

fa-regular-400.woff

fa-regular-400.woff

214 ms

fa-light-300.woff

fa-light-300.woff

266 ms

Code_Pro_Demo-webfont.woff

Code_Pro_Demo-webfont.woff

272 ms

fa-brands-400.woff

fa-brands-400.woff

268 ms

js

js

89 ms

analytics.js

analytics.js

23 ms

collect

collect

45 ms

saffron-grange.svg

saffron-grange.svg

152 ms

saffron-grange-icon.svg

saffron-grange-icon.svg

86 ms

www.saffrongrange.com

www.saffrongrange.com

696 ms

collect

collect

144 ms

js

js

67 ms

home-bottle-full-cuvee.jpg

home-bottle-full-cuvee.jpg

78 ms

woocommerce-smallscreen.css

woocommerce-smallscreen.css

33 ms

Accessibility Review

saffrongrange.com accessibility score

96

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

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

High

Page has valid source maps

SEO Factors

saffrongrange.com SEO score

82

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

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

saffrongrange.com

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