Tools & Wizards About Us
cannalogic.com screenshot

Report Summary

  • 49

    Performance

    Renders faster than
    67% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

cannalogic.com

Dispensary POS App, Dispensary Point Of Sale Software

Page Load Speed

5.4 sec in total

First Response

581 ms

Resources Loaded

3.8 sec

Page Rendered

1.1 sec

cannalogic.com screenshot

About Website

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

Looking for medical dispensary software or dispensary POS app? CannaLogic's POS dispensary mobile platform is now available to all dispensaries worldwide.

Visit cannalogic.com

Key Findings

We analyzed Cannalogic.com page load time and found that the first response time was 581 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

cannalogic.com performance score

49

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

27/100

10%

LCP (Largest Contentful Paint)

Value9.9 s

0/100

25%

SI (Speed Index)

Value4.8 s

67/100

10%

TBT (Total Blocking Time)

Value290 ms

80/100

30%

CLS (Cumulative Layout Shift)

Value0.009

100/100

15%

TTI (Time to Interactive)

Value14.1 s

9/100

10%

Network Requests Diagram

cannalogic.com

581 ms

cannalogic.com

803 ms

webflow.css

589 ms

js

57 ms

jquery-3.5.1.min.js

757 ms

Our browser made a total of 51 requests to load all elements on the main page. We found that 41% of them (21 requests) were addressed to the original Cannalogic.com, 25% (13 requests) were made to Embed.tawk.to and 18% (9 requests) were made to Cannalogicimg.s3.ca-central-1.amazonaws.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Cannalogic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 228.3 kB (5%)

Content Size

5.0 MB

After Optimization

4.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Cannalogic.com main page is 5.0 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. 40% of websites need less resources to load. Images take 4.5 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 11.9 kB

  • Original 15.1 kB
  • After minification 11.9 kB
  • After compression 3.2 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 3.2 kB, which is 21% 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 11.9 kB or 79% of the original size.

Image Optimization

-2%

Potential reduce by 90.5 kB

  • Original 4.5 MB
  • After minification 4.4 MB

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. Cannalogic images are well optimized though.

JavaScript Optimization

-23%

Potential reduce by 96.5 kB

  • Original 414.8 kB
  • After minification 414.8 kB
  • After compression 318.3 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 96.5 kB or 23% of the original size.

CSS Optimization

-52%

Potential reduce by 29.4 kB

  • Original 56.9 kB
  • After minification 56.9 kB
  • After compression 27.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. Cannalogic.com needs all CSS files to be minified and compressed as it can save up to 29.4 kB or 52% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (35%)

Requests Now

43

After Optimization

28

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

cannalogic.com

cannalogic.com

581 ms

cannalogic.com

cannalogic.com

803 ms

webflow.css

webflow.css

589 ms

js

js

57 ms

jquery-3.5.1.min.js

jquery-3.5.1.min.js

757 ms

webflow.js

webflow.js

1533 ms

css

css

31 ms

default

default

115 ms

img-light.jpg

img-light.jpg

224 ms

main.png

main.png

234 ms

unnamed.jpg

unnamed.jpg

236 ms

img1.png

img1.png

229 ms

img2.png

img2.png

253 ms

compliant.png

compliant.png

199 ms

img8.png

img8.png

272 ms

img9.png

img9.png

277 ms

logo.png

logo.png

288 ms

loading.gif

loading.gif

585 ms

twitter-icon-white.svg

twitter-icon-white.svg

325 ms

facebook-icon-white.svg

facebook-icon-white.svg

520 ms

instagram-icon-white.svg

instagram-icon-white.svg

577 ms

dribbble-icon-white.svg

dribbble-icon-white.svg

576 ms

compliant-res.png

compliant-res.png

1608 ms

img9-res.png

img9-res.png

1265 ms

form-block-bg.jpg

form-block-bg.jpg

1148 ms

menu.png

menu.png

775 ms

thecannabisindustry.png

thecannabisindustry.png

972 ms

metrc-logo.png

metrc-logo.png

1159 ms

twitter.png

twitter.png

1108 ms

linkedin.png

linkedin.png

1188 ms

youtube.png

youtube.png

1314 ms

android1.png

android1.png

1347 ms

ios1.png

ios1.png

1354 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX8.ttf

37 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

43 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

48 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

49 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf

48 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX8.ttf

47 ms

twk-arr-find-polyfill.js

twk-arr-find-polyfill.js

51 ms

twk-object-values-polyfill.js

twk-object-values-polyfill.js

64 ms

twk-event-polyfill.js

twk-event-polyfill.js

57 ms

twk-entries-polyfill.js

twk-entries-polyfill.js

57 ms

twk-iterator-polyfill.js

twk-iterator-polyfill.js

64 ms

twk-promise-polyfill.js

twk-promise-polyfill.js

60 ms

twk-main.js

twk-main.js

59 ms

twk-vendor.js

twk-vendor.js

109 ms

twk-chunk-vendors.js

twk-chunk-vendors.js

68 ms

twk-chunk-common.js

twk-chunk-common.js

74 ms

twk-runtime.js

twk-runtime.js

74 ms

twk-app.js

twk-app.js

85 ms

Accessibility Review

cannalogic.com accessibility score

82

Accessibility Issues

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

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

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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

cannalogic.com SEO score

92

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

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

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

cannalogic.com

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