Tools & Wizards About Us
winery-sage.com screenshot

Report Summary

  • 42

    Performance

    Renders faster than
    61% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

winery-sage.com

Winery-Sage.com | Your Site for Wine Suggestions & Research

Page Load Speed

4.3 sec in total

First Response

397 ms

Resources Loaded

3.8 sec

Page Rendered

113 ms

winery-sage.com screenshot

About Website

Visit winery-sage.com now to see the best up-to-date Winery Sage content for United States and also check out these interesting facts you probably never knew about winery-sage.com

We are a free online resource for wine novices who need advice and aficionados who want to research Wineries, Regions & Varietals with no ads or deceiving links

Visit winery-sage.com

Key Findings

We analyzed Winery-sage.com page load time and found that the first response time was 397 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

winery-sage.com performance score

42

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

55/100

10%

LCP (Largest Contentful Paint)

Value12.4 s

0/100

25%

SI (Speed Index)

Value7.6 s

26/100

10%

TBT (Total Blocking Time)

Value430 ms

64/100

30%

CLS (Cumulative Layout Shift)

Value0.105

88/100

15%

TTI (Time to Interactive)

Value12.3 s

15/100

10%

Network Requests Diagram

winery-sage.com

397 ms

index.php

737 ms

style.css

344 ms

pinit.js

20 ms

ga.js

35 ms

Our browser made a total of 70 requests to load all elements on the main page. We found that 40% of them (28 requests) were addressed to the original Winery-sage.com, 26% (18 requests) were made to Platform.twitter.com and 19% (13 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Winery-sage.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 64.6 kB (9%)

Content Size

739.9 kB

After Optimization

675.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Winery-sage.com main page is 739.9 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. 60% of websites need less resources to load. Images take 642.3 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 61.9 kB

  • Original 78.3 kB
  • After minification 76.3 kB
  • After compression 16.4 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 61.9 kB or 79% of the original size.

Image Optimization

-0%

Potential reduce by 2.1 kB

  • Original 642.3 kB
  • After minification 640.2 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. Winery Sage images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 53 B

  • Original 17.3 kB
  • After minification 17.2 kB
  • After compression 17.2 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

-25%

Potential reduce by 484 B

  • Original 2.0 kB
  • After minification 2.0 kB
  • After compression 1.5 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. Winery-sage.com needs all CSS files to be minified and compressed as it can save up to 484 B or 25% of the original size.

Requests Breakdown

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

Requests Now

68

After Optimization

37

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 68 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Winery Sage. 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 as a result speed up the page load time.

Network Requests Diagram

winery-sage.com

winery-sage.com

397 ms

index.php

index.php

737 ms

style.css

style.css

344 ms

pinit.js

pinit.js

20 ms

ga.js

ga.js

35 ms

likebox.php

likebox.php

114 ms

pinit_fg_en_rect_red_20.png

pinit_fg_en_rect_red_20.png

12 ms

winery-sage-logo2.png

winery-sage-logo2.png

804 ms

spacer.gif

spacer.gif

340 ms

navbg.png

navbg.png

376 ms

bg1.jpg

bg1.jpg

378 ms

btn_mailing_list.png

btn_mailing_list.png

377 ms

btn_include_your_wine.png

btn_include_your_wine.png

374 ms

Varietal-That-Fits-Your-Taste-Positive.jpg

Varietal-That-Fits-Your-Taste-Positive.jpg

769 ms

Who.jpg

Who.jpg

777 ms

Food-to-Pair.jpg

Food-to-Pair.jpg

775 ms

Varietal-to-Pair.jpg

Varietal-to-Pair.jpg

778 ms

wine-barrell.jpg

wine-barrell.jpg

776 ms

Special.jpg

Special.jpg

1208 ms

Education.jpg

Education.jpg

1175 ms

Wine-Trails.jpg

Wine-Trails.jpg

1122 ms

Blog.jpg

Blog.jpg

1130 ms

widgets.js

widgets.js

103 ms

pinit_main.js

pinit_main.js

4 ms

count.json

count.json

30 ms

__utm.gif

__utm.gif

11 ms

Ql-UNnxapLj.css

Ql-UNnxapLj.css

29 ms

DaPJf3IFK7Z.js

DaPJf3IFK7Z.js

32 ms

Y4zFOWmUObv.js

Y4zFOWmUObv.js

56 ms

8O2J-mJIMh1.js

8O2J-mJIMh1.js

57 ms

QCHZeiE_shc.js

QCHZeiE_shc.js

57 ms

4aFcRp6-srT.js

4aFcRp6-srT.js

57 ms

Mgao39tvtRW.js

Mgao39tvtRW.js

55 ms

0bio7TMsDws.js

0bio7TMsDws.js

63 ms

kY8eYg-9-SS.js

kY8eYg-9-SS.js

65 ms

DJbp39Fn87q.js

DJbp39Fn87q.js

63 ms

p55HfXW__mM.js

p55HfXW__mM.js

62 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

100 ms

332956621_915464556263131_8504603549512868009_n.jpg

332956621_915464556263131_8504603549512868009_n.jpg

105 ms

272093621_6882630888478320_7777016864156004707_n.jpg

272093621_6882630888478320_7777016864156004707_n.jpg

52 ms

QoMTH0SpLC5.js

QoMTH0SpLC5.js

25 ms

UXtr_j2Fwe-.png

UXtr_j2Fwe-.png

21 ms

settings

settings

87 ms

timeline.e108540dddc96e4b707f5cf259a582d7.js

timeline.e108540dddc96e4b707f5cf259a582d7.js

21 ms

WinerySage

WinerySage

56 ms

polyfills-a40ef1678bae11e696dba45124eadd70.js

polyfills-a40ef1678bae11e696dba45124eadd70.js

22 ms

runtime-b1c52fd0a13ead5fcf6b.js

runtime-b1c52fd0a13ead5fcf6b.js

48 ms

modules-96ebc7ac3ad66d681a3d.js

modules-96ebc7ac3ad66d681a3d.js

69 ms

main-babd9234dc048fb47339.js

main-babd9234dc048fb47339.js

77 ms

_app-a9c9f1a99e4414675fb1.js

_app-a9c9f1a99e4414675fb1.js

96 ms

%5BscreenName%5D-0517bdda27d5006a5a2d.js

%5BscreenName%5D-0517bdda27d5006a5a2d.js

101 ms

_buildManifest.js

_buildManifest.js

114 ms

_ssgManifest.js

_ssgManifest.js

114 ms

8526.0c32a8f0cfc5749221a3.js

8526.0c32a8f0cfc5749221a3.js

23 ms

1755.07a49c40b12af4f75780.js

1755.07a49c40b12af4f75780.js

23 ms

8283.f3e5048cca7cef5eed7f.js

8283.f3e5048cca7cef5eed7f.js

24 ms

3077.44bfeb00af01bc4020f6.js

3077.44bfeb00af01bc4020f6.js

47 ms

1362.42d432e02f7980bca032.js

1362.42d432e02f7980bca032.js

38 ms

4956.c4e51ef593974b9db0bb.js

4956.c4e51ef593974b9db0bb.js

64 ms

5893.d500bd2a89ded806aa73.js

5893.d500bd2a89ded806aa73.js

29 ms

Varietal-over.jpg

Varietal-over.jpg

365 ms

Who-over.jpg

Who-over.jpg

346 ms

Food-over.jpg

Food-over.jpg

376 ms

Varietal-to-Pair-over.jpg

Varietal-to-Pair-over.jpg

373 ms

wine-barrell-over.jpg

wine-barrell-over.jpg

354 ms

Special-over.jpg

Special-over.jpg

339 ms

Education-over.jpg

Education-over.jpg

680 ms

Blog-over.jpg

Blog-over.jpg

675 ms

Wine-Trails-over.jpg

Wine-Trails-over.jpg

726 ms

Festival-over.jpg

Festival-over.jpg

708 ms

Accessibility Review

winery-sage.com accessibility score

87

Accessibility Issues

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

<frame> or <iframe> elements do not have a title

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

winery-sage.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

winery-sage.com SEO score

75

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Winery-sage.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 Winery-sage.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

winery-sage.com

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