Website review, no card needed

abdragons.com logo

abdragons.com website review

Visit site (opens in a new tab)Reviewed 16 November 202650 issues · 98 checks

This review found 50 issues worth fixing on abdragons.com, 20 of them high impact, across 98 checks. The most urgent: reduce unused JavaScript. 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.1 s1.6 sMay 30Nov 141.9 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.8 s
Jun 6, 20261.8 s
Jun 13, 20261.8 s
Jun 20, 20261.7 s
Jun 27, 20261.7 s
Jul 4, 20261.7 s
Jul 11, 20261.7 s
Jul 18, 20261.7 s
Jul 25, 20261.7 s
Aug 1, 20261.7 s
Aug 8, 20261.7 s
Aug 15, 20261.7 s
Aug 22, 20261.7 s
Aug 29, 20261.7 s
Sep 5, 20261.8 s
Sep 12, 20261.8 s
Sep 19, 20261.9 s
Sep 26, 20262.0 s
Oct 3, 20262.0 s
Oct 10, 20262.1 s
Oct 17, 20262.1 s
Oct 24, 20262.0 s
Oct 31, 20261.9 s
Nov 7, 20261.9 s
Nov 14, 20261.9 s
Real-visitor tap response (INP)75th percentile, phones
106 ms95 msMay 30Nov 1499 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 202696 ms
Jun 6, 202697 ms
Jun 13, 202697 ms
Jun 20, 202698 ms
Jun 27, 2026102 ms
Jul 4, 2026102 ms
Jul 11, 2026103 ms
Jul 18, 202696 ms
Jul 25, 202696 ms
Aug 1, 202696 ms
Aug 8, 202696 ms
Aug 15, 202696 ms
Aug 22, 2026100 ms
Aug 29, 2026104 ms
Sep 5, 2026104 ms
Sep 12, 2026105 ms
Sep 19, 2026104 ms
Sep 26, 2026103 ms
Oct 3, 2026102 ms
Oct 10, 2026101 ms
Oct 17, 2026102 ms
Oct 24, 202698 ms
Oct 31, 202696 ms
Nov 7, 202699 ms
Nov 14, 202699 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 abdragons.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. abdragons.com at 0.5 s0.5 s
  2. abdragons.com at 0.9 s0.9 s
  3. abdragons.com at 1.4 s1.4 s
  4. abdragons.com at 1.8 s1.8 s
  5. abdragons.com at 2.3 s2.3 s
  6. abdragons.com at 2.8 s2.8 s
  7. abdragons.com at 3.2 s3.2 s
  8. abdragons.com at 3.7 s3.7 s

Speed

14 to fix37
  • Reduce unused JavaScript

    3.0 s · 2.5 MB

    About 2.5 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.0 s faster on a phone.

  • Improve image delivery

    3.8 s · 857 KiB

    11 images could be 857 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.8 s faster on a phone.

  • Use efficient cache lifetimes

    2.0 s · 872 KiB

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

  • Render-blocking requests

    1.5 s

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

  • Mobile performance score: 37

    37/100

    Your mobile performance score is 37. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 4.5 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google CDN, Google Tag Manager and elfsight.com and others), adding 6.4 MB and 1.9 s of main-thread time.

  • Reduce unused CSS

    910 ms · 169 KiB

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

  • Google CDN adds 493 ms

    493 ms

    Google CDN costs a phone 493 ms of main-thread work and 1.4 MB 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 Tag Manager adds 387 ms

    387 ms

    Google Tag Manager costs a phone 387 ms of main-thread work and 879 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.

  • Bigcommerce adds 179 ms

    179 ms

    Bigcommerce costs a phone 179 ms of main-thread work and 2.0 MB 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.

  • elfsight.com adds 297 ms

    297 ms

    elfsight.com costs a phone 297 ms of main-thread work and 14 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.

  • LivePerson adds 135 ms

    135 ms

    LivePerson costs a phone 135 ms of main-thread work and 1.3 MB 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.

  • 1,877 HTML elements

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

  • 18 long tasks on the main thread

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

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • Legacy JavaScript

    43 KiB

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

  • Minify JavaScript

    15 KiB

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

  • Minify CSS

    4 KiB

    4 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 19 ms

    19 ms

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

Core Web Vitals

9 to fix0
  • 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.

  • Real-user CLS: 0.61

    0.61

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

  • Largest Contentful Paint: 22.9 s

    22.9 s

    Your largest element takes 22.9 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: 41.0 s

    41.0 s

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

  • Speed Index: 12.0 s

    12.0 s

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

  • Total Blocking Time: 565 ms

    565 ms

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

  • First Contentful Paint: 2.9 s

    2.9 s

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

  • Cumulative Layout Shift: 0.196

    0.196

    The layout shifts by 0.196 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • 12 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +3%

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

  • Largest content (LCP) held steady for real visitors

    +5%

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

1 checks passed
  • Real-user FCP: 1.3 s

    1.3 s

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

Images and page weight

4 to fix52
  • Page weight: 7.7 MB in 180 requests

    7.7 MB

    Your homepage downloads 7.7 MB in 180 requests on a phone: scripts 4.8 MB (66), images 1.7 MB (29) and other files 428 KiB (38). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    Cute_Playful_December_2026_Christmas_Calendar.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 6 images far larger than shown

    480 KiB

    6 images are downloaded at several times the size a phone draws them, for example chatgpt-image-aug-26-2026-02-10-18-pm.png at 1,402 px wide, shown at 350 px. Resized copies would save about 480 KiB.

  • 3 images below the first screen load straight away

    3 images further down the page (569 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 2.2 g of CO₂ per visit

    2.18 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

12 to fixGoogle 7585
  • 13 text elements with low contrast

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

  • 11 tap targets too small

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

  • Hidden but focusable

    8 elements hidden from screen readers can still receive keyboard focus.

  • Orphan list items

    Some list items are not inside a list.

  • Frames without titles

    3 frames have no title, so screen-reader users cannot tell what they contain.

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

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

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 10 links without text

    10 visible links have no text or label, so screen readers cannot say where they go.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

  • Headings skip levels

    Headings skip levels (h2 → h4, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 42 images in the HTML carry an alt attribute.

  • 46 automated accessibility rules passed

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

SEO

3 to fixGoogle 10083
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 165 internal links, 14 external

    The homepage links to 165 pages on abdragons.com and 14 external pages.

5 checks passed
  • Meta description: 151 characters

    Your meta description is 151 characters: “ABDragons is the premier seller of feeder insects - including Dubia roaches, mealworms, and superfoods - for your beard…”.

  • Title: 46 characters

    Your title is a healthy 46 characters: “Dubia Roaches, Bearded Dragon Food | ABDragons”.

  • Canonical URL set

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

  • 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://abdragons.com/xmlsitemap.php.

AI search readiness

1 to fix88
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

  • No llms.txt

    There is no https://abdragons.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 (556 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 13 pages without a meta description

    https://abdragons.com/shop-by-pet-1, https://abdragons.com/bearded-dragon-1, https://abdragons.com/lizard, https://abdragons.com/gecko, https://abdragons.com/chameleon and https://abdragons.com/frog and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

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

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

3 to fixGoogle 6985
  • 7 small tap targets

    7 of 26 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 2 deprecated browser APIs that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “bx2 is not defined”.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Content security policy”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix81
  • No social proof

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

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • 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 276 words of copy

    The homepage carries about 276 words of visible text.

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop All Feeders” and “Shop By Pet”.

  • 21 calls to action

    The homepage has 21 calls to action, for example “Shop By Pet”, “ABDragons Unique Shop” and “Shop Now”.

  • 4 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Meta Pixel.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 3 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

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

  • 24 cookies set on arrival

    24

    Opening the homepage sets 24 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.

  • 48 other companies contacted

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

Upkeep, stack and company

Stack

Framework
jQuery
E-commerce
BigCommerce
Analytics
Google Analytics | Google Tag Manager
Hosting
Bigcommerce Inc.

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 50 issues on abdragons.com, including 23 speed issues, 3 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