Tools & Wizards About Us
triuswines.com screenshot

Report Summary

  • 49

    Performance

    Renders faster than
    67% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

triuswines.com

Home | Trius Winery

Page Load Speed

5.6 sec in total

First Response

800 ms

Resources Loaded

4.5 sec

Page Rendered

318 ms

triuswines.com screenshot

About Website

Click here to check amazing Trius Wines content for Canada. Otherwise, check out these important facts you probably never knew about triuswines.com

Home

Visit triuswines.com

Key Findings

We analyzed Triuswines.com page load time and found that the first response time was 800 ms and then it took 4.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

triuswines.com performance score

49

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

9/100

10%

LCP (Largest Contentful Paint)

Value7.3 s

5/100

25%

SI (Speed Index)

Value8.7 s

16/100

10%

TBT (Total Blocking Time)

Value80 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value20.2 s

2/100

10%

Network Requests Diagram

triuswines.com

800 ms

www.triuswines.com

1705 ms

jquery-1.7.2.min.js

294 ms

scripts.js

144 ms

swfobject.js

140 ms

Our browser made a total of 62 requests to load all elements on the main page. We found that 82% of them (51 requests) were addressed to the original Triuswines.com, 5% (3 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Triuswines.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 598.3 kB (36%)

Content Size

1.6 MB

After Optimization

1.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Triuswines.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. 50% of websites need less resources to load. Images take 885.1 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 17.2 kB

  • Original 22.8 kB
  • After minification 20.1 kB
  • After compression 5.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. This page needs HTML code to be minified as it can gain 2.7 kB, which is 12% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 17.2 kB or 76% of the original size.

Image Optimization

-2%

Potential reduce by 20.5 kB

  • Original 885.1 kB
  • After minification 864.6 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. Trius Wines images are well optimized though.

JavaScript Optimization

-75%

Potential reduce by 459.2 kB

  • Original 611.2 kB
  • After minification 510.3 kB
  • After compression 152.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 459.2 kB or 75% of the original size.

CSS Optimization

-84%

Potential reduce by 101.4 kB

  • Original 120.8 kB
  • After minification 88.0 kB
  • After compression 19.4 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. Triuswines.com needs all CSS files to be minified and compressed as it can save up to 101.4 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 28 (49%)

Requests Now

57

After Optimization

29

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

triuswines.com

triuswines.com

800 ms

www.triuswines.com

www.triuswines.com

1705 ms

jquery-1.7.2.min.js

jquery-1.7.2.min.js

294 ms

scripts.js

scripts.js

144 ms

swfobject.js

swfobject.js

140 ms

scripts-trius.js

scripts-trius.js

70 ms

fonts.js

fonts.js

75 ms

buttons.js

buttons.js

11 ms

styles.css

styles.css

156 ms

widgets.css

widgets.css

116 ms

prototype.js

prototype.js

387 ms

ccard.js

ccard.js

160 ms

validation.js

validation.js

249 ms

builder.js

builder.js

187 ms

effects.js

effects.js

265 ms

dragdrop.js

dragdrop.js

322 ms

controls.js

controls.js

326 ms

slider.js

slider.js

282 ms

js.js

js.js

321 ms

form.js

form.js

342 ms

menu.js

menu.js

343 ms

translate.js

translate.js

358 ms

cookies.js

cookies.js

362 ms

main.css

main.css

371 ms

main-trius.css

main-trius.css

430 ms

webFontLoader.css

webFontLoader.css

414 ms

itrac.js

itrac.js

217 ms

webfont.js

webfont.js

16 ms

css

css

26 ms

KT3KS9Aol4WfR6Vas8kNcg.woff

KT3KS9Aol4WfR6Vas8kNcg.woff

10 ms

9k-RPmcnxYEPm8CNFsH2gg.woff

9k-RPmcnxYEPm8CNFsH2gg.woff

13 ms

wkfQbvfT_02e2IWO3yYueQ.woff

wkfQbvfT_02e2IWO3yYueQ.woff

34 ms

tile.jpg

tile.jpg

98 ms

9781Loft.jpg

9781Loft.jpg

324 ms

Slide-winter.jpg

Slide-winter.jpg

255 ms

1.jpg

1.jpg

128 ms

2.jpg

2.jpg

204 ms

5.jpg

5.jpg

177 ms

6.jpg

6.jpg

227 ms

05444.jpg

05444.jpg

191 ms

T-Red-oscars-website.jpg

T-Red-oscars-website.jpg

214 ms

ACJ3566.jpg

ACJ3566.jpg

276 ms

trius_red_2012_1.jpg

trius_red_2012_1.jpg

235 ms

TriusTWS.JPG

TriusTWS.JPG

275 ms

banner1.jpg

banner1.jpg

259 ms

ga.js

ga.js

9 ms

wrapper_bg.png

wrapper_bg.png

256 ms

header_bg.png

header_bg.png

276 ms

btn_visit.png

btn_visit.png

284 ms

btn_drink.png

btn_drink.png

288 ms

btn_eat.png

btn_eat.png

321 ms

btn_join.png

btn_join.png

298 ms

btn_ask.png

btn_ask.png

306 ms

btn_buyOnline.gif

btn_buyOnline.gif

316 ms

HP_3Col_bg.gif

HP_3Col_bg.gif

317 ms

__utm.gif

__utm.gif

43 ms

btn_buyWine.gif

btn_buyWine.gif

287 ms

stayConnected_bg2.jpg

stayConnected_bg2.jpg

298 ms

btn_submit.gif

btn_submit.gif

303 ms

c

c

77 ms

getAllAppDefault.esi

getAllAppDefault.esi

1478 ms

print.css

print.css

51 ms

Accessibility Review

triuswines.com accessibility score

85

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

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

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

triuswines.com best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

triuswines.com SEO score

77

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

High

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

High

Document uses legible font sizes

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

triuswines.com

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