Tools & Wizards About Us
tweed.com screenshot

Report Summary

  • 47

    Performance

    Renders faster than
    65% 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

  • 71

    SEO

    Google-friendlier than
    30% of websites

tweed.com

Tweed CAN

Page Load Speed

1.1 sec in total

First Response

250 ms

Resources Loaded

713 ms

Page Rendered

129 ms

tweed.com screenshot

About Website

Welcome to tweed.com homepage info - get ready to check Tweed best content for Canada right away, or after learning these important things about tweed.com

Tweed CAN

Visit tweed.com

Key Findings

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

Performance Metrics

tweed.com performance score

47

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

80/100

10%

LCP (Largest Contentful Paint)

Value7.5 s

4/100

25%

SI (Speed Index)

Value4.5 s

71/100

10%

TBT (Total Blocking Time)

Value710 ms

42/100

30%

CLS (Cumulative Layout Shift)

Value0.013

100/100

15%

TTI (Time to Interactive)

Value9.4 s

31/100

10%

Network Requests Diagram

www.tweed.com

250 ms

preloads.js

301 ms

load_feature-9f951eb7d8d53973c719de211f807d63af81c644e5b9a6ae72661ac408d472f6.js

34 ms

features-1c0b396bd4d054b94abae1eb6a1bd6ba47beb35525c57a217c77a862ff06d83f.js

32 ms

theme.css

61 ms

Our browser made a total of 20 requests to load all elements on the main page. We found that 90% of them (18 requests) were addressed to the original Tweed.com, 5% (1 request) were made to Assets.adobedtm.com and 5% (1 request) were made to Assets.customer.io. The less responsive or slowest element that took the longest time to load (301 ms) belongs to the original domain Tweed.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 75.3 kB (6%)

Content Size

1.3 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-75%

Potential reduce by 75.2 kB

  • Original 99.9 kB
  • After minification 87.7 kB
  • After compression 24.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. This page needs HTML code to be minified as it can gain 12.1 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 75.2 kB or 75% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 924.9 kB
  • After minification 924.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. Tweed images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 83 B

  • Original 225.7 kB
  • After minification 225.7 kB
  • After compression 225.6 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 24 B

  • Original 25.7 kB
  • After minification 25.7 kB
  • After compression 25.7 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. Tweed.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 9 (47%)

Requests Now

19

After Optimization

10

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.tweed.com

www.tweed.com

250 ms

preloads.js

preloads.js

301 ms

load_feature-9f951eb7d8d53973c719de211f807d63af81c644e5b9a6ae72661ac408d472f6.js

load_feature-9f951eb7d8d53973c719de211f807d63af81c644e5b9a6ae72661ac408d472f6.js

34 ms

features-1c0b396bd4d054b94abae1eb6a1bd6ba47beb35525c57a217c77a862ff06d83f.js

features-1c0b396bd4d054b94abae1eb6a1bd6ba47beb35525c57a217c77a862ff06d83f.js

32 ms

theme.css

theme.css

61 ms

theme.js

theme.js

49 ms

launch-ENdb250d91a8644da48a74a4649ad2df31.min.js

launch-ENdb250d91a8644da48a74a4649ad2df31.min.js

23 ms

shopify-perf-kit-unstable.min.js

shopify-perf-kit-unstable.min.js

40 ms

trekkie.storefront.a1ad2ab43a5932ff96084a0e2e69f51ba73ddbec.min.js

trekkie.storefront.a1ad2ab43a5932ff96084a0e2e69f51ba73ddbec.min.js

46 ms

shop_events_listener-61fa9e0a912c675e178777d2b27f6cbd482f8912a6b0aa31fa3515985a8cd626.js

shop_events_listener-61fa9e0a912c675e178777d2b27f6cbd482f8912a6b0aa31fa3515985a8cd626.js

45 ms

shopify-boomerang-1.0.0.min.js

shopify-boomerang-1.0.0.min.js

45 ms

track-eu.js

track-eu.js

22 ms

tweed-logo-green.svg

tweed-logo-green.svg

45 ms

products-composite.png

products-composite.png

89 ms

beverage-composite.png

beverage-composite.png

56 ms

flower-composite.png

flower-composite.png

91 ms

prj-composite--cropped.png

prj-composite--cropped.png

52 ms

vapes.png

vapes.png

98 ms

oils.png

oils.png

267 ms

softgels.png

softgels.png

127 ms

Accessibility Review

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

button, link, and menuitem elements do not have accessible names.

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

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

tweed.com SEO score

71

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

High

Image elements do not have [alt] attributes

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

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

tweed.com

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