Website review, no card needed
drkilligans.com website review
Visit site (opens in a new tab)Reviewed 16 November 202639 issues · 93 checks
This review found 39 issues worth fixing on drkilligans.com, 15 of them high impact, across 93 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
74C- #82,636 of 117,615 reviewed websitesbeats 26%
- #52,412 of 66,923 online storesbeats 18%
- #49,330 of 61,018 Shopify storesbeats 16%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 1.7 s |
| Jun 6, 2026 | 1.9 s |
| Jun 13, 2026 | 2.1 s |
| Jun 20, 2026 | 2.2 s |
| Jun 27, 2026 | 2.2 s |
| Jul 4, 2026 | 2.2 s |
| Jul 11, 2026 | 2.2 s |
| Jul 18, 2026 | 2.3 s |
| Jul 25, 2026 | 2.4 s |
| Aug 1, 2026 | 2.4 s |
| Aug 8, 2026 | 2.5 s |
| Aug 15, 2026 | 2.5 s |
| Aug 22, 2026 | 2.5 s |
| Aug 29, 2026 | 2.4 s |
| Sep 5, 2026 | 2.4 s |
| Sep 12, 2026 | 2.3 s |
| Sep 19, 2026 | 2.2 s |
| Sep 26, 2026 | 2.2 s |
| Oct 3, 2026 | 2.2 s |
| Oct 10, 2026 | 2.2 s |
| Oct 17, 2026 | 2.3 s |
| Oct 24, 2026 | 2.3 s |
| Oct 31, 2026 | 2.4 s |
| Nov 7, 2026 | 2.5 s |
| Nov 14, 2026 | 2.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 132 ms |
| Jun 6, 2026 | 138 ms |
| Jun 13, 2026 | 139 ms |
| Jun 20, 2026 | 143 ms |
| Jun 27, 2026 | 141 ms |
| Jul 4, 2026 | 137 ms |
| Jul 11, 2026 | 136 ms |
| Jul 18, 2026 | 135 ms |
| Jul 25, 2026 | 138 ms |
| Aug 1, 2026 | 144 ms |
| Aug 8, 2026 | 150 ms |
| Aug 15, 2026 | 153 ms |
| Aug 22, 2026 | 152 ms |
| Aug 29, 2026 | 154 ms |
| Sep 5, 2026 | 154 ms |
| Sep 12, 2026 | 154 ms |
| Sep 19, 2026 | 155 ms |
| Sep 26, 2026 | 155 ms |
| Oct 3, 2026 | 154 ms |
| Oct 10, 2026 | 154 ms |
| Oct 17, 2026 | 154 ms |
| Oct 24, 2026 | 153 ms |
| Oct 31, 2026 | 156 ms |
| Nov 7, 2026 | 163 ms |
| Nov 14, 2026 | 157 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
How it loaded on a phone
0.5 s
1.0 s
1.6 s
2.1 s
2.6 s
3.1 s
3.7 s
4.2 s
Speed
Reduce unused JavaScript
2.2 s · 561 KiBAbout 561 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.2 s faster on a phone.
Mobile performance score: 40
40/100Your mobile performance score is 40. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 7.7 s
A phone's processor spends 7.7 s on main-thread work while loading, 3.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3,008 HTML elements
The page has 3,008 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, Clarity and Google Tag Manager and others), adding 1.8 MB and 1.5 s of main-thread time.
Improve image delivery
900 ms · 705 KiB24 images could be 705 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 900 ms faster on a phone.
Use efficient cache lifetimes
450 ms · 259 KiB23 files are served with short cache lifetimes, so returning visitors download them again (259 KiB).
Shopify adds 547 ms
547 msShopify costs a phone 547 ms of main-thread work and 735 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.
Reduce unused CSS
300 ms · 46 KiBAbout 46 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
Render-blocking requests
300 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.
Clarity adds 266 ms
266 msClarity costs a phone 266 ms of main-thread work and 28 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.
Klaviyo adds 160 ms
160 msKlaviyo costs a phone 160 ms of main-thread work and 321 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 219 ms. During a long task the page ignores taps.
Legacy JavaScript
150 ms · 29 KiBPolyfills for old browsers add 29 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
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.
Minify CSS
5 KiB5 KiB could be saved by minifying CSS.
Minify JavaScript
2 KiB2 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 11 ms
11 msYour server sent the HTML in 11 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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: 17.4 s
17.4 sYour largest element takes 17.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Black Friday early access sale with up to 40% off sitewide.…”.
Time to Interactive: 20.4 s
20.4 sThe page becomes fully interactive after 20.4 s. Good is under 3.8 s.
Speed Index: 9.6 s
9.6 sVisually, the page fills in at 9.6 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 890 ms
890 msScripts block taps and scrolling for 890 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 3.4 s
3.4 sThe first text or image appears after 3.4 s on a phone. Good is under 1.8 s.
Real-user LCP: 3.4 s
3.4 sReal visitors wait 3.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Largest content (LCP) got 40% slower for real visitors
+40%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.7 s to 2.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.2 s
2.2 sReal visitors see the first content after 2.2 s (75th percentile). Good is under 1.8 s.
14 images without width and height
14 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 19% slower for real visitors
+19%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 132 ms to 157 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user INP: 163 ms
163 msReal visitors wait 163 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user TTFB: 748 ms
748 msReal visitors wait 748 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.026
0.026The layout barely moves while loading (CLS 0.026, good is under 0.1).
Images and page weight
Page weight: 4.9 MB in 438 requests
4.9 MBYour homepage downloads 4.9 MB in 438 requests on a phone: scripts 1.7 MB (137), other files 1.4 MB (241) and images 1.4 MB (41). Under 2 MB keeps phones on slow connections fast.
2 images below the first screen load straight away
2 images further down the page (68 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.4 g of CO₂ per visit
1.39 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.39 g of CO₂e: 166.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
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.
5 tap targets too small
5 tap targets are too small or too close together to hit reliably with a finger.
All page content should be contained by landmarks (6 elements)
All page content should be contained by landmarks: 6 elements on the page fail this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
4 links without text
4 visible links have no text or label, so screen readers cannot say where they go.
ARIA role should be appropriate for the element (2 elements)
ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 74 images in the HTML carry an alt attribute.
53 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 59 WCAG 2.2 A/AA and best-practice rules on the phone render: 53 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is long (258 characters)
Your meta description is 258 characters; Google truncates after about 160, so the end of your pitch is cut.
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.
141 internal links, 18 external
The homepage links to 141 pages on drkilligans.com and 18 external pages.
7 checks passed
One H1 headline
Your main headline reads: “Dr. Killigan's”.
Title: 50 characters
Your title is a healthy 50 characters: “Dr. Killigan's Plant-Powered Pest Control Products”.
Canonical URL set
The canonical URL is https://drkilligans.com/.
Structured data in place
Structured data found: BreadcrumbList, Organization and WebSite.
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://drkilligans.com/sitemap.xml.
AI search readiness
4 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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,108 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://drkilligans.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a meta description
https://drkilligans.com/collections/best-selling-collection has no meta description, so Google writes the search snippet from whatever text it finds.
4 pages slow to respond
https://drkilligans.com/collections/fleas, https://drkilligans.com/products/doom-and-bloom-plant-spray, https://drkilligans.com/collections/cockroaches and https://drkilligans.com/collections/fruit-flies took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 56 found) and read each the way a search engine does.
6 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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 15 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://drkilligans.com/.
20 small tap targets
20 of 76 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.”).
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_TUNNEL_CONNECTION_FAILED”.
Requests the notification permission on page load
Requests the notification permission on page load.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
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.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
About 706 words of copy
The homepage carries about 706 words of visible text.
6 checks passed
10 calls to action
The homepage has 10 calls to action, for example “Shop by Pest”, “Shop by Product” and “Shop All”.
6 short forms
6 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 5 testimonial or review blocks and 1 trust badge.
Analytics in place
Analytics detected: Google Tag Manager, Microsoft Clarity and Hotjar.
Phone number on the homepage
Your phone number is on the homepage.
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
10 trackers load before any consent
10Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Klaviyo and 5 mores (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.
46 cookies set on arrival
46Opening the homepage sets 46 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.
70 other companies contacted
Loading the homepage contacts 70 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 drkilligans.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 19 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Intelligems A B Testing · Mntn · Fly Bundles Upsells · Triplewhale · Gorgias Live Chat Helpdesk · Microsoft Clarity · Klaviyo Email Marketing Sms · Echo All In One Fixed Bundles · Aftersell · Rivo Loyalty Rewards Referrals · Pushowl · Applovin Shop Integration · Page Speed Optimizer · Upcart · trafficmanager.net · socialsnowball.io · octaneai.com · 9gtb.com · onetext.com
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
- Analytics
- Google Tag Manager | Hotjar | Microsoft Clarity
- Hosting
- Shopify
Company
- Headquarters
- Redding
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 39 issues on drkilligans.com, including 22 speed issues, 2 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.