Tools & Wizards About Us
ginkgowinery.com screenshot

Report Summary

  • 57

    Performance

    Renders faster than
    73% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

ginkgowinery.com

Ginkgo Forest Winery | Ginkgo Mattawa | Ginkgo Tacoma | Ginkgo Winery | Wahluke Slope AVA | Washington State Wines | Ginkgo Winery | Organic Wines

Page Load Speed

631 ms in total

First Response

116 ms

Resources Loaded

515 ms

Page Rendered

0 ms

ginkgowinery.com screenshot

About Website

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

Gingko Forest Winery and Vineyards, located in the Wahluke Slope AVA, Mattawa, Washington. Tasting Rooms are located in Mattawa and Tacoma, Washington where you can sample and purchase award winning w...

Visit ginkgowinery.com

Key Findings

We analyzed Ginkgowinery.com page load time and found that the first response time was 116 ms and then it took 515 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.

Performance Metrics

ginkgowinery.com performance score

57

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

50/100

10%

LCP (Largest Contentful Paint)

Value3.6 s

61/100

25%

SI (Speed Index)

Value3.7 s

85/100

10%

TBT (Total Blocking Time)

Value780 ms

37/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value11.3 s

19/100

10%

Network Requests Diagram

www.ginkgowinery.com

116 ms

minified.js

32 ms

focus-within-polyfill.js

64 ms

polyfill.min.js

30 ms

thunderbolt-commons.e7839053.bundle.min.js

154 ms

Our browser made a total of 33 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Ginkgowinery.com, 64% (21 requests) were made to Static.wixstatic.com and 27% (9 requests) were made to Static.parastorage.com. The less responsive or slowest element that took the longest time to load (155 ms) relates to the external source Static.parastorage.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 874.4 kB (55%)

Content Size

1.6 MB

After Optimization

709.7 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Ginkgowinery.com main page is 1.6 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. 45% of websites need less resources to load. HTML takes 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 824.3 kB

  • Original 1.0 MB
  • After minification 1.0 MB
  • After compression 182.6 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 824.3 kB or 82% of the original size.

Image Optimization

-14%

Potential reduce by 45.9 kB

  • Original 316.8 kB
  • After minification 270.9 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, Ginkgo Winery needs image optimization as it can save up to 45.9 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-2%

Potential reduce by 4.2 kB

  • Original 260.4 kB
  • After minification 260.3 kB
  • After compression 256.1 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.

Requests Breakdown

Number of requests can be reduced by 10 (31%)

Requests Now

32

After Optimization

22

  • Images
  • JavaScript

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

Network Requests Diagram

www.ginkgowinery.com

www.ginkgowinery.com

116 ms

minified.js

minified.js

32 ms

focus-within-polyfill.js

focus-within-polyfill.js

64 ms

polyfill.min.js

polyfill.min.js

30 ms

thunderbolt-commons.e7839053.bundle.min.js

thunderbolt-commons.e7839053.bundle.min.js

154 ms

main.760485a2.bundle.min.js

main.760485a2.bundle.min.js

155 ms

main.renderer.1d21f023.bundle.min.js

main.renderer.1d21f023.bundle.min.js

119 ms

lodash.min.js

lodash.min.js

154 ms

react.production.min.js

react.production.min.js

120 ms

react-dom.production.min.js

react-dom.production.min.js

120 ms

siteTags.bundle.min.js

siteTags.bundle.min.js

120 ms

a786c1_cf1435f7f2164885b3574705ddafadbaf000.jpg

a786c1_cf1435f7f2164885b3574705ddafadbaf000.jpg

95 ms

bundle.min.js

bundle.min.js

87 ms

GinkgoForestWinery-logo-black.png

GinkgoForestWinery-logo-black.png

62 ms

leaf-background.png

leaf-background.png

62 ms

a786c1_ceabbc4e25f3430a80b55dce901a316b~mv2.jpg

a786c1_ceabbc4e25f3430a80b55dce901a316b~mv2.jpg

63 ms

a786c1_f3b4ff69f16044bc8346a20891acd0b0~mv2.jpg

a786c1_f3b4ff69f16044bc8346a20891acd0b0~mv2.jpg

62 ms

a786c1_851f687b10c6489e9d8ac6700b778774~mv2.jpg

a786c1_851f687b10c6489e9d8ac6700b778774~mv2.jpg

62 ms

a786c1_b9ac03d3b3824d669e57d40b48d551b9~mv2.webp

a786c1_b9ac03d3b3824d669e57d40b48d551b9~mv2.webp

64 ms

a786c1_b9ac03d3b3824d669e57d40b48d551b9~mv2.webp

a786c1_b9ac03d3b3824d669e57d40b48d551b9~mv2.webp

65 ms

a786c1_5ef08bfb7faf4d029ef193bc4702962c~mv2.webp

a786c1_5ef08bfb7faf4d029ef193bc4702962c~mv2.webp

65 ms

a786c1_5ef08bfb7faf4d029ef193bc4702962c~mv2.webp

a786c1_5ef08bfb7faf4d029ef193bc4702962c~mv2.webp

65 ms

a786c1_2c6ecdd32ef04510a1628f827648e89b~mv2.webp

a786c1_2c6ecdd32ef04510a1628f827648e89b~mv2.webp

67 ms

a786c1_2c6ecdd32ef04510a1628f827648e89b~mv2.webp

a786c1_2c6ecdd32ef04510a1628f827648e89b~mv2.webp

66 ms

a786c1_e88a8d87a36d4bda8dda8f8f8cb9eab4~mv2.jpg

a786c1_e88a8d87a36d4bda8dda8f8f8cb9eab4~mv2.jpg

67 ms

a786c1_071b1cf375394df8b55f65a8f1953d9a~mv2.jpg

a786c1_071b1cf375394df8b55f65a8f1953d9a~mv2.jpg

66 ms

a786c1_a92a83f5898b47648454f55b2d1c89ce~mv2.jpg

a786c1_a92a83f5898b47648454f55b2d1c89ce~mv2.jpg

66 ms

a786c1_611273fe7ccb4442ad851640d45e1a4c~mv2.jpg

a786c1_611273fe7ccb4442ad851640d45e1a4c~mv2.jpg

68 ms

a786c1_ea8a2e1b5b534d81b87bdc9619d9c782~mv2.jpg

a786c1_ea8a2e1b5b534d81b87bdc9619d9c782~mv2.jpg

69 ms

a786c1_1b1f54bb527b42759d99797dfe400fbb~mv2.jpg

a786c1_1b1f54bb527b42759d99797dfe400fbb~mv2.jpg

68 ms

a786c1_27164908dfb242d497eb253bfb3786ff~mv2.jpg

a786c1_27164908dfb242d497eb253bfb3786ff~mv2.jpg

69 ms

a786c1_c164c8ac734a4e4291542bb8aa6ca31c~mv2.jpg

a786c1_c164c8ac734a4e4291542bb8aa6ca31c~mv2.jpg

69 ms

a786c1_1e37465ceb0c4e669809aa1cff5478b0~mv2.jpg

a786c1_1e37465ceb0c4e669809aa1cff5478b0~mv2.jpg

70 ms

Accessibility Review

ginkgowinery.com accessibility score

86

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

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

Buttons do not have an accessible name

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

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

ginkgowinery.com SEO score

91

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

ginkgowinery.com

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