Website review, no card needed

gascannabisco.com logo

gascannabisco.com website review

Visit site (opens in a new tab)Reviewed 7 November 202647 issues · 86 checks

This review found 47 issues worth fixing on gascannabisco.com, 19 of them high impact, across 86 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
2.8 s1.9 sJun 6Sep 122.2 s
Show as table
DateReal-visitor load time (LCP)
Jun 6, 20262.7 s
Jun 13, 20262.5 s
Jun 20, 20262.6 s
Jun 27, 20262.0 s
Jul 4, 20262.0 s
Jul 11, 20262.0 s
Jul 18, 20262.0 s
Aug 15, 20262.4 s
Aug 22, 20262.3 s
Aug 29, 20262.3 s
Sep 5, 20262.2 s
Sep 12, 20262.2 s
Real-visitor tap response (INP)75th percentile, phones
2.4 s2.1 sJun 27Sep 122.4 s
Show as table
DateReal-visitor tap response (INP)
Jun 27, 20262.2 s
Jul 4, 20262.1 s
Jul 11, 20262.1 s
Jul 18, 20262.1 s
Aug 29, 20262.4 s
Sep 5, 20262.4 s
Sep 12, 20262.4 s

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of gascannabisco.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. gascannabisco.com at 0.9 s0.9 s
  2. gascannabisco.com at 1.9 s1.9 s
  3. gascannabisco.com at 2.8 s2.8 s
  4. gascannabisco.com at 3.7 s3.7 s
  5. gascannabisco.com at 4.6 s4.6 s
  6. gascannabisco.com at 5.6 s5.6 s
  7. gascannabisco.com at 6.5 s6.5 s
  8. gascannabisco.com at 7.4 s7.4 s

Speed

10 to fix88
  • Render-blocking requests

    1.6 s

    12 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.

  • 4,116 HTML elements

    The page has 4,116 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Use efficient cache lifetimes

    1.2 MB

    57 files are served with short cache lifetimes, so returning visitors download them again (1.2 MB).

  • 8 third-party services on the page

    8 third-party services load with your homepage (Adobe Tag Manager, sprinklr.com and Facebook and others), adding 1.9 MB and 867 ms of main-thread time.

  • Mobile performance score: 88

    88/100

    Your mobile performance score is 88. Pages that score under 90 lose visitors before the first paint.

  • Reduce unused JavaScript

    977 KiB

    About 977 KiB of JavaScript is downloaded but never used on this page.

  • Main-thread work: 3.1 s

    A phone's processor spends 3.1 s on main-thread work while loading, 1.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • sprinklr.com adds 167 ms

    167 ms

    sprinklr.com costs a phone 167 ms of main-thread work and 417 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Google Maps adds 73 ms

    73 ms

    Google Maps costs a phone 73 ms of main-thread work and 329 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Google CDN adds 64 ms

    64 ms

    Google CDN costs a phone 64 ms of main-thread work and 349 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Improve image delivery

    166 KiB

    1 image could be 166 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 6 long tasks on the main thread

    6 long tasks block the main thread while loading, the longest for 161 ms. During a long task the page ignores taps.

  • Legacy JavaScript

    30 KiB

    Polyfills for old browsers add 30 KiB JavaScript that modern phones do not need.

  • Minify JavaScript

    7 KiB

    7 KiB could be saved by minifying JavaScript.

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

1 checks passed
  • Server response: 153 ms

    153 ms

    Your server sent the HTML in 153 ms, well inside Google's 600 ms guideline.

Core Web Vitals

4 to fix96
  • Time to Interactive: 18.6 s

    18.6 s

    The page becomes fully interactive after 18.6 s. Good is under 3.8 s.

  • Speed Index: 6.5 s

    6.5 s

    Visually, the page fills in at 6.5 s (Speed Index). Good is under 3.4 s.

  • 110 images without width and height

    110 images have no width and height attributes, so the layout jumps as each one loads.

  • First Contentful Paint: 2.0 s

    2.0 s

    The first text or image appears after 2.0 s on a phone. Good is under 1.8 s.

  • Tap response (INP) got 11% slower for real visitors

    +11%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 2.2 s to 2.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

4 checks passed
  • Largest content (LCP) got 16% faster for real visitors

    -16%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.7 s to 2.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Total Blocking Time: 192 ms

    192 ms

    Scripts block the page for only 192 ms while loading. Good is under 200 ms.

  • Largest Contentful Paint: 2.0 s

    2.0 s

    Your largest element renders in 2.0 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Cari Cari Troli Login Buka Menu Saya Navigation”.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

2 to fix75
  • Page weight: 2.7 MB in 167 requests

    2.7 MB

    Your homepage downloads 2.7 MB in 167 requests on a phone: scripts 2.3 MB (84), images 260 KiB (13) and HTML 90 KiB (7). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    161 KiB

    1 image is downloaded at several times the size a phone draws it, for example maha168-logo.png at 2,719 px wide, shown at 200 px. Resized copies would save about 161 KiB.

  • 1 image in older formats

    1 image (169 KiB) is JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

  • About 0.8 g of CO₂ per visit

    0.76 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.76 g of CO₂e: 91.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

17 to fixGoogle 5880
  • 160 text elements with low contrast

    160 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 147 tap targets too small

    147 tap targets are too small or too close together to hit reliably with a finger.

  • Certain ARIA roles must be contained by particular parents (18 elements)

    Certain ARIA roles must be contained by particular parents: 18 elements on the page fail this check, rated critical by axe-core.

  • 6 buttons without a name

    6 buttons have no accessible name, so screen readers announce just “button”.

  • Certain ARIA roles must contain particular children (3 elements)

    Certain ARIA roles must contain particular children: 3 elements on the page fail this check, rated critical by axe-core.

  • Invalid ARIA attributes

    1 element use ARIA attributes their role does not allow, which confuses screen readers.

  • ARIA attributes must conform to valid values (1 element)

    ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

  • Unlabelled dropdowns

    1 dropdown has no label.

  • ARIA dialog and alertdialog nodes should have an accessible name (32 elements)

    ARIA dialog and alertdialog nodes should have an accessible name: 32 elements on the page fail this check, rated serious by axe-core.

  • Orphan list items

    Some list items are not inside a list.

  • Links must have discernible text (1 element)

    Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

  • 3 images without alt text

    3 images have no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (124 elements)

    All page content should be contained by landmarks: 124 elements on the page fail this check, rated moderate by axe-core.

  • 4 form fields without a label

    4 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Elements use prohibited ARIA attributes

    Elements use prohibited ARIA attributes (1 element).

  • ARIA role should be appropriate for the element (1 element)

    ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (33 elements).

1 checks passed
  • 54 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 69 WCAG 2.2 A/AA and best-practice rules on the phone render: 54 passed and 15 failed. 7 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

5 to fixGoogle 7780
  • Title is long (69 characters)

    Your title is 69 characters, so Google will cut it off around 60: “MAHA168 | Edukasi Dasar Volatilitas Slot Online dan Cara Mengelolanya”.

  • 3 H1 headlines

    There are 3 <h1> headlines (“MAHA168 | Edukasi Dasar Volatilitas Slot Online d…”, “MAHA168 | Edukasi Dasar Volatilitas Slot Online d…” and “MAHA168 | Edukasi Dasar Volatilitas Slot Online d…”). One clear main headline is easier for people and search engines.

  • 25 links crawlers can't follow

    25 links have no real href, so search engines can't follow them.

  • Structured data has 4 problems

    Structured data found (BreadcrumbList, FAQPage, ItemList and OfferCatalog) but with 4 problems, for example “Organization: logo is not an absolute URL ("assets/maha168-logo.png")”.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 69 internal links, 61 external

    The homepage links to 69 pages on gascannabisco.com and 61 external pages.

5 checks passed
  • Meta description: 148 characters

    Your meta description is 148 characters: “Pelajari dasar volatilitas slot online di MAHA168 — perbedaan volatilitas rendah, sedang & tinggi, serta cara mengelola…”.

  • Canonical URL set

    The canonical URL is https://www.gascannabisco.com/.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://gascannabisco.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.gascannabisco.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

3 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (3,692 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix0
  • 3 linked pages are broken

    Your homepage links to https://www.gascannabisco.com/kebijakan-privasi, https://www.gascannabisco.com/legal and https://www.gascannabisco.com/sitemap, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 3 internal pages checked

    We fetched 3 pages linked from your homepage and read each the way a search engine does.

Best practices

5 to fixGoogle 5469
  • 5 broken images

    5 images failed to load on a phone, for example https://www.gascannabisco.com/#.

  • 46 small tap targets

    46 of 61 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Unsafe attempt to load URL https://www.samsung.com/etc.clientlibs/samsung/clientlibs/consumer/global/clientlib-common/r…”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix79
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • About 1,757 words of copy

    The homepage carries about 1,757 words of visible text.

5 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “MAHA168 Explore Shop” and “Shop”.

  • 9 short forms

    9 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 70 testimonial or review blocks and a star rating.

  • Analytics in place

    Analytics detected: Cloudflare Web Analytics.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Pinterest Tag (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

  • 13 cookies set on arrival

    13

    Opening the homepage sets 13 cookies (measured from a US location before any click).

  • No consent tool detected

    No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

  • 27 other companies contacted

    Loading the homepage contacts 27 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at gascannabisco.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

E-commerce
Shopify;Shopify Plus
Hosting
Cloudflare

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 47 issues on gascannabisco.com, including 14 speed issues, 5 SEO issues and 2 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25