Report Summary

  • 76

    Performance

    Renders faster than
    84% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 62% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

Page Load Speed

1.4 sec in total

First Response

539 ms

Resources Loaded

713 ms

Page Rendered

162 ms

cannabisdoc.com screenshot

About Website

Click here to check amazing Cannabisdoc content. Otherwise, check out these important facts you probably never knew about cannabisdoc.com

Visit cannabisdoc.com

Key Findings

We analyzed Cannabisdoc.com page load time and found that the first response time was 539 ms and then it took 875 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

cannabisdoc.com performance score

76

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

34/100

10%

LCP (Largest Contentful Paint)

Value3.8 s

55/100

25%

SI (Speed Index)

Value3.5 s

88/100

10%

TBT (Total Blocking Time)

Value180 ms

92/100

30%

CLS (Cumulative Layout Shift)

Value0.099

90/100

15%

TTI (Time to Interactive)

Value4.2 s

86/100

10%

Network Requests Diagram

cannabisdoc.com

539 ms

combo.gif

183 ms

border4.gif

149 ms

cannyborder.gif

162 ms

urchin.js

7 ms

Our browser made a total of 6 requests to load all elements on the main page. We found that 67% of them (4 requests) were addressed to the original Cannabisdoc.com, 33% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (539 ms) belongs to the original domain Cannabisdoc.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.9 kB (29%)

Content Size

10.1 kB

After Optimization

7.2 kB

In fact, the total size of Cannabisdoc.com main page is 10.1 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only 5% of websites need less resources to load. Javascripts take 6.8 kB which makes up the majority of the site volume.

HTML Optimization

-60%

Potential reduce by 1.9 kB

  • Original 3.2 kB
  • After minification 3.1 kB
  • After compression 1.3 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 1.9 kB or 60% of the original size.

JavaScript Optimization

-14%

Potential reduce by 971 B

  • Original 6.8 kB
  • After minification 6.8 kB
  • After compression 5.9 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 971 B or 14% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

5

After Optimization

5

The browser has sent 5 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cannabisdoc. According to our analytics all requests are already optimized.

Accessibility Review

cannabisdoc.com accessibility score

86

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

Document doesn't have a <title> element

High

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

Best Practices

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

cannabisdoc.com SEO score

75

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

Document doesn't have a <title> element

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

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

    N/A

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cannabisdoc.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Cannabisdoc.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

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