Tools & Wizards About Us
weedshop.no screenshot

Report Summary

  • 43

    Performance

    Renders faster than
    62% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 39% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

weedshop.no

Arkiv for Produkter - Weedshop.no

Page Load Speed

1.7 sec in total

First Response

480 ms

Resources Loaded

1.1 sec

Page Rendered

109 ms

weedshop.no screenshot

About Website

Welcome to weedshop.no homepage info - get ready to check Weedshop best content right away, or after learning these important things about weedshop.no

Visit weedshop.no

Key Findings

We analyzed Weedshop.no page load time and found that the first response time was 480 ms and then it took 1.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

weedshop.no performance score

43

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.3 s

1/100

10%

LCP (Largest Contentful Paint)

Value15.2 s

0/100

25%

SI (Speed Index)

Value12.4 s

3/100

10%

TBT (Total Blocking Time)

Value220 ms

87/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value12.1 s

16/100

10%

Network Requests Diagram

weedshop.no

480 ms

stylesheet.css

98 ms

frontlogo.jpg

278 ms

corner_left.gif

285 ms

pixel_trans.gif

284 ms

Our browser made a total of 33 requests to load all elements on the main page. We found that 76% of them (25 requests) were addressed to the original Weedshop.no, 21% (7 requests) were made to Static.xx.fbcdn.net and 3% (1 request) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (565 ms) belongs to the original domain Weedshop.no.

Page Optimization Overview & Recommendations

Page size can be reduced by 35.5 kB (22%)

Content Size

159.7 kB

After Optimization

124.2 kB

  • HTML
  • Images
  • CSS

In fact, the total size of Weedshop.no main page is 159.7 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. 25% of websites need less resources to load. Images take 127.1 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 22.8 kB

  • Original 26.2 kB
  • After minification 24.1 kB
  • After compression 3.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 22.8 kB or 87% of the original size.

Image Optimization

-6%

Potential reduce by 7.4 kB

  • Original 127.1 kB
  • After minification 119.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. Weedshop images are well optimized though.

CSS Optimization

-82%

Potential reduce by 5.3 kB

  • Original 6.4 kB
  • After minification 4.7 kB
  • After compression 1.1 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. Weedshop.no needs all CSS files to be minified and compressed as it can save up to 5.3 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 12 (38%)

Requests Now

32

After Optimization

20

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

weedshop.no

weedshop.no

480 ms

stylesheet.css

stylesheet.css

98 ms

frontlogo.jpg

frontlogo.jpg

278 ms

corner_left.gif

corner_left.gif

285 ms

pixel_trans.gif

pixel_trans.gif

284 ms

corner_right_left.gif

corner_right_left.gif

282 ms

button_quick_find.gif

button_quick_find.gif

288 ms

icon.gif

icon.gif

286 ms

icon.gif

icon.gif

372 ms

arrow_right.gif

arrow_right.gif

375 ms

buddy_grinder_mini_l.jpg

buddy_grinder_mini_l.jpg

379 ms

table_background_default.gif

table_background_default.gif

375 ms

fan101650_2_l.jpg

fan101650_2_l.jpg

376 ms

st-025_l.jpg

st-025_l.jpg

379 ms

minibordvekt_l.jpg

minibordvekt_l.jpg

464 ms

s-l300_l.jpg

s-l300_l.jpg

506 ms

raw_box_l.jpg

raw_box_l.jpg

505 ms

rollies_l.jpg

rollies_l.jpg

506 ms

raw_conetips_l.jpg

raw_conetips_l.jpg

506 ms

GB-080_l.jpg

GB-080_l.jpg

506 ms

hpspakke_l.jpg

hpspakke_l.jpg

558 ms

corner_right.gif

corner_right.gif

560 ms

led90_l.jpg

led90_l.jpg

565 ms

backg.gif

backg.gif

558 ms

backg2.gif

backg2.gif

557 ms

likebox.php

likebox.php

171 ms

hDvwL1_H7g-.css

hDvwL1_H7g-.css

91 ms

q68gy-v_YMF.js

q68gy-v_YMF.js

125 ms

FJmpeSpHpjS.js

FJmpeSpHpjS.js

177 ms

0wM5s1Khldu.js

0wM5s1Khldu.js

143 ms

1bNoFZUdlYZ.js

1bNoFZUdlYZ.js

143 ms

I6-MnjEovm5.js

I6-MnjEovm5.js

21 ms

pQrUxxo5oQp.js

pQrUxxo5oQp.js

19 ms

Accessibility Review

weedshop.no accessibility score

73

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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.

Best Practices

weedshop.no best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

weedshop.no SEO score

75

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

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

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

    NO

  • Language Claimed

    EN

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Weedshop.no can be misinterpreted by Google and other search engines. Our service has detected that Norwegian is used on the page, and it does not match the claimed English language. Our system also found out that Weedshop.no 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

weedshop.no

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