Website review, no card needed

gasdrawls.com logo

gasdrawls.com website review

Visit site (opens in a new tab)Reviewed 10 November 202630 issues · 75 checks

This review found 30 issues worth fixing on gasdrawls.com, 11 of them high impact, across 75 checks. The most urgent: improve image delivery. 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.0 s1.3 sMay 23Nov 71.4 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.8 s
May 30, 20261.8 s
Jun 6, 20261.7 s
Jun 13, 20261.7 s
Jun 20, 20261.7 s
Jun 27, 20261.7 s
Jul 4, 20261.7 s
Jul 11, 20261.8 s
Jul 18, 20261.8 s
Jul 25, 20261.8 s
Aug 1, 20261.8 s
Aug 8, 20261.8 s
Aug 15, 20261.8 s
Aug 22, 20261.8 s
Aug 29, 20261.8 s
Sep 5, 20261.8 s
Sep 12, 20261.9 s
Sep 19, 20261.9 s
Sep 26, 20261.9 s
Oct 3, 20261.9 s
Oct 10, 20261.8 s
Oct 17, 20261.8 s
Oct 24, 20261.8 s
Oct 31, 20261.5 s
Nov 7, 20261.4 s
Real-visitor tap response (INP)75th percentile, phones
267 ms134 msMay 23Nov 7149 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026203 ms
May 30, 2026199 ms
Jun 6, 2026200 ms
Jun 13, 2026188 ms
Jun 20, 2026187 ms
Jun 27, 2026193 ms
Jul 4, 2026194 ms
Jul 11, 2026209 ms
Jul 18, 2026224 ms
Jul 25, 2026226 ms
Aug 1, 2026229 ms
Aug 8, 2026233 ms
Aug 15, 2026234 ms
Aug 22, 2026235 ms
Aug 29, 2026239 ms
Sep 5, 2026245 ms
Sep 12, 2026243 ms
Sep 19, 2026252 ms
Sep 26, 2026242 ms
Oct 3, 2026243 ms
Oct 10, 2026243 ms
Oct 17, 2026232 ms
Oct 24, 2026239 ms
Oct 31, 2026154 ms
Nov 7, 2026149 ms

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 gasdrawls.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. gasdrawls.com at 0.6 s0.6 s
  2. gasdrawls.com at 1.2 s1.2 s
  3. gasdrawls.com at 1.8 s1.8 s
  4. gasdrawls.com at 2.4 s2.4 s
  5. gasdrawls.com at 3.0 s3.0 s
  6. gasdrawls.com at 3.6 s3.6 s
  7. gasdrawls.com at 4.2 s4.2 s
  8. gasdrawls.com at 4.8 s4.8 s

Speed

8 to fix52
  • Improve image delivery

    1.1 s · 1.0 MB

    23 images could be 1.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.

  • YouTube adds 1.4 s

    1.4 s

    YouTube costs a phone 1.4 s of main-thread work and 3.9 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • 7,591 HTML elements

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

  • Main-thread work: 5.5 s

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

  • Reduce unused JavaScript

    2.5 MB

    About 2.5 MB of JavaScript is downloaded but never used on this page.

  • 8 third-party services on the page

    8 third-party services load with your homepage (YouTube, minmaxify.com and kiwisizing.com and others), adding 4.6 MB and 1.8 s of main-thread time.

  • Mobile performance score: 52

    52/100

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

  • Render-blocking requests

    900 ms

    5 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.

  • Reduce unused CSS

    150 ms · 110 KiB

    About 110 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • Use efficient cache lifetimes

    243 KiB

    21 files are served with short cache lifetimes, so returning visitors download them again (243 KiB).

  • 13 long tasks on the main thread

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

  • Minify JavaScript

    150 ms · 4 KiB

    4 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    19 KiB

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

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

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

1 checks passed
  • Server response: 17 ms

    17 ms

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

Core Web Vitals

6 to fix67
  • Fails Core Web Vitals for real visitors

    Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

  • Largest Contentful Paint: 10.5 s

    10.5 s

    Your largest element takes 10.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

  • Time to Interactive: 44.1 s

    44.1 s

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

  • Speed Index: 12.9 s

    12.9 s

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

  • Real-user INP: 235 ms

    235 ms

    Real visitors wait 235 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Total Blocking Time: 519 ms

    519 ms

    Scripts block taps and scrolling for 519 ms in total while the page loads. Good is under 200 ms.

8 checks passed
  • Real-user LCP: 1.7 s

    1.7 s

    Real visitors wait 1.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.4 s

    1.4 s

    Real visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 412 ms

    412 ms

    Real visitors wait 412 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Tap response (INP) got 25% faster for real visitors

    -25%

    Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 203 ms to 149 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) got 21% faster for real visitors

    -21%

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

  • First Contentful Paint: 1.2 s

    1.2 s

    The first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix63
  • Page weight: 8.9 MB in 347 requests

    8.9 MB

    Your homepage downloads 8.9 MB in 347 requests on a phone: scripts 4.3 MB (130), images 2.6 MB (55) and other files 860 KiB (126). Under 2 MB keeps phones on slow connections fast.

  • 32 images below the first screen load straight away

    32 images further down the page (1.6 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 3 images in older formats

    3 images (315 KiB) are 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 2.5 g of CO₂ per visit

    2.51 g

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

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

1 to fixGoogle 10094
  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

1 checks passed
  • 17 automated accessibility rules passed

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

SEO

4 to fixGoogle 10080
  • Title is short (10 characters)

    Your title is only 10 characters: “GAS DRAWLS”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is short (22 characters)

    Your meta description is only 22 characters: “MF DOOM Official Store”. 70 to 160 characters is enough to sell the click.

  • 2 H1 headlines

    There are 2 <h1> headlines (“GAS DRAWLS” and “MF DOOM × Sanford GreeneCollectionzz Artist Series”). One clear main headline is easier for people and search engines.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 203 internal links, 0 external

    The homepage links to 203 pages on gasdrawls.com and 0 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://gasdrawls.com/.

  • Structured data in place

    Structured data found: Organization.

  • 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://gasdrawls.com/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

    There is no https://gasdrawls.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.

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

  • Text is in the HTML

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

Other pages

2 to fix90
  • 7 pages without a meta description

    https://gasdrawls.com/pages/mf-doom-sanford-greene, https://gasdrawls.com/collections/shop, https://gasdrawls.com/collections/merch, https://gasdrawls.com/collections/music, https://gasdrawls.com/collections/metalface-records and https://gasdrawls.com/pages/stream and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

  • 9 pages without an H1

    https://gasdrawls.com/pages/mf-doom-sanford-greene, https://gasdrawls.com/collections/shop, https://gasdrawls.com/collections/merch, https://gasdrawls.com/collections/music, https://gasdrawls.com/products/gasdrawls-gift-card and https://gasdrawls.com/collections/metalface-records and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 77 found) and read each the way a search engine does.

5 checks passed
  • Linked pages load

    9 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 9 pages that loaded have a <title>.

Best practices

2 to fixGoogle 7391
  • 5 third-party cookies

    5 third-party cookies are 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 “Failed to load resource: net::ERR_FAILED”.

  • Browser-reported issues

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

2 checks passed
  • Tap targets are thumb-sized

    33 of 33 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix67
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

  • About 1,064 words of copy

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

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP THE DROP”.

  • 7 calls to action

    The homepage has 7 calls to action, for example “Shop the drop”, “SHOP” and “CONTACT”.

  • 33 short forms

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

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 1 more (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.

  • 27 cookies set on arrival

    27

    Opening the homepage sets 27 cookies, 1 of them by other companies (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.

  • 38 other companies contacted

    Loading the homepage contacts 38 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 gasdrawls.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 10 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Attentive · Klaviyo Email Marketing Sms · Minmaxify Order Limits · Triplewhale · Back In Stock · elfsight.com · kiwisizing.com · chimpstatic.com · shopclimb.com · attn.tv

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

E-commerce
Shopify
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 30 issues on gasdrawls.com, including 14 speed issues, 4 SEO issues and 3 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