Website review, no card needed
johnnydangandco.com website review
Visit site (opens in a new tab)Reviewed 9 November 202636 issues · 87 checks
This review found 36 issues worth fixing on johnnydangandco.com, 15 of them high impact, across 87 checks. The most urgent: shopify adds 5.5 s. 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
78C- #61,769 of 123,087 reviewed websitesbeats 44%
- #40,390 of 69,407 online storesbeats 36%
- #38,581 of 63,192 Shopify storesbeats 33%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 2.0 s |
| May 30, 2026 | 2.0 s |
| Jun 6, 2026 | 2.0 s |
| Jun 13, 2026 | 2.0 s |
| Jun 20, 2026 | 2.0 s |
| Jun 27, 2026 | 2.0 s |
| Jul 4, 2026 | 2.0 s |
| Jul 11, 2026 | 2.1 s |
| Jul 18, 2026 | 2.1 s |
| Jul 25, 2026 | 2.1 s |
| Aug 1, 2026 | 2.0 s |
| Aug 8, 2026 | 2.0 s |
| Aug 15, 2026 | 2.0 s |
| Aug 22, 2026 | 2.0 s |
| Aug 29, 2026 | 2.0 s |
| Sep 5, 2026 | 2.0 s |
| Sep 12, 2026 | 2.0 s |
| Sep 19, 2026 | 2.0 s |
| Sep 26, 2026 | 1.9 s |
| Oct 3, 2026 | 1.9 s |
| Oct 10, 2026 | 1.8 s |
| Oct 17, 2026 | 1.8 s |
| Oct 24, 2026 | 1.7 s |
| Oct 31, 2026 | 1.7 s |
| Nov 7, 2026 | 1.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 193 ms |
| May 30, 2026 | 192 ms |
| Jun 6, 2026 | 196 ms |
| Jun 13, 2026 | 203 ms |
| Jun 20, 2026 | 202 ms |
| Jun 27, 2026 | 200 ms |
| Jul 4, 2026 | 200 ms |
| Jul 11, 2026 | 199 ms |
| Jul 18, 2026 | 204 ms |
| Jul 25, 2026 | 205 ms |
| Aug 1, 2026 | 204 ms |
| Aug 8, 2026 | 204 ms |
| Aug 15, 2026 | 205 ms |
| Aug 22, 2026 | 211 ms |
| Aug 29, 2026 | 213 ms |
| Sep 5, 2026 | 207 ms |
| Sep 12, 2026 | 211 ms |
| Sep 19, 2026 | 209 ms |
| Sep 26, 2026 | 203 ms |
| Oct 3, 2026 | 203 ms |
| Oct 10, 2026 | 192 ms |
| Oct 17, 2026 | 186 ms |
| Oct 24, 2026 | 180 ms |
| Oct 31, 2026 | 192 ms |
| Nov 7, 2026 | 209 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.4 s
0.9 s
1.3 s
1.7 s
2.2 s
2.6 s
3.1 s
3.5 s
Speed
Shopify adds 5.5 s
5.5 sShopify costs a phone 5.5 s of main-thread work and 1.5 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.
Reduce unused JavaScript
3.0 s · 805 KiBAbout 805 KiB 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.
Main-thread work: 14.1 s
A phone's processor spends 14.1 s on main-thread work while loading, 8.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
4,421 HTML elements
The page has 4,421 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, vitals.app and nice-team.net and others), adding 2.1 MB and 6.1 s of main-thread time.
Improve image delivery
1.6 MB32 images could be 1.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Mobile performance score: 52
52/100Your mobile performance score is 52. Pages that score under 90 lose visitors before the first paint.
vitals.app adds 351 ms
351 msvitals.app costs a phone 351 ms of main-thread work and 299 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 · 76 KiBAbout 76 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 ms5 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.
17 long tasks on the main thread
17 long tasks block the main thread while loading, the longest for 142 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
70 KiB12 files are served with short cache lifetimes, so returning visitors download them again (70 KiB).
Minify JavaScript
44 KiB44 KiB could be saved by minifying JavaScript.
Legacy JavaScript
24 KiBPolyfills for old browsers add 24 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: 15 ms
15 msYour server sent the HTML in 15 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: 25.2 s
25.2 sYour largest element takes 25.2 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: 31.0 s
31.0 sThe page becomes fully interactive after 31.0 s. Good is under 3.8 s.
Speed Index: 8.3 s
8.3 sVisually, the page fills in at 8.3 s (Speed Index). Good is under 3.4 s.
Real-user INP: 239 ms
239 msReal visitors wait 239 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
First Contentful Paint: 2.7 s
2.7 sThe first text or image appears after 2.7 s on a phone. Good is under 1.8 s.
Total Blocking Time: 460 ms
460 msScripts block taps and scrolling for 460 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
+4%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 193 ms to 209 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user LCP: 2.1 s
2.1 sReal visitors wait 2.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.7 s
1.7 sReal visitors see the first content after 1.7 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 711 ms
711 msReal visitors wait 711 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 14% faster for real visitors
-14%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 2.0 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 22.9 MB in 544 requests
22.9 MBYour homepage downloads 22.9 MB in 544 requests on a phone: media 14.4 MB (5), images 4.9 MB (52) and scripts 1.9 MB (204). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
66 KiB1 image is downloaded at several times the size a phone draws it, for example ChatGPT_Image_Mar_4_2026_05_13_24_PM.png at 389 px wide, shown at 80 px. Resized copies would save about 66 KiB.
2 images below the first screen load straight away
2 images further down the page (127 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 6.5 g of CO₂ per visit
6.50 gBy the Sustainable Web Design model, a visit to your homepage emits about 6.50 g of CO₂e: 779.8 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
20 text elements with low contrast
20 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Hidden but focusable
3 elements hidden from screen readers can still receive keyboard focus.
Interactive controls must not be nested (1 element)
Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
5 images without alt text
5 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
16 links without text
16 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
50 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 57 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 7 failed. 3 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 (298 characters)
Your meta description is 298 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.
98 internal links, 4 external
The homepage links to 98 pages on johnnydangandco.com and 4 external pages.
7 checks passed
One H1 headline
Your main headline reads: “Johnny Dang & Co”.
Title: 42 characters
Your title is a healthy 42 characters: “Johnny Dang & Co | Call or Text 2812488888”.
Canonical URL set
The canonical URL is https://johnnydangandco.com/.
Structured data in place
Structured data found: Organization.
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://johnnydangandco.com/sitemap.xml.
AI search readiness
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.
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.
Text is in the HTML
Your server sends the page's text in the HTML (1,819 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://johnnydangandco.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
4 pages share 2 titles
https://johnnydangandco.com/collections/chains-1 and https://johnnydangandco.com/collections/chains-all all use the title “Chains – Johnny Dang & Co”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.
13 pages without a meta description
https://johnnydangandco.com/pages/about-us-1, https://johnnydangandco.com/collections/pendants-1, https://johnnydangandco.com/collections/chains-1, https://johnnydangandco.com/collections/bracelet, https://johnnydangandco.com/collections/rings-1 and https://johnnydangandco.com/collections/valentines-collection and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.
15 pages without an H1
https://johnnydangandco.com/pages/about-us-1, https://johnnydangandco.com/collections/pendants-1, https://johnnydangandco.com/collections/chains-1, https://johnnydangandco.com/collections/bracelet, https://johnnydangandco.com/collections/rings-1 and https://johnnydangandco.com/collections/earrings and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://johnnydangandco.com/collections/chains-all has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 36 found) and read each the way a search engine does.
4 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.
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 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
2 checks passed
Tap targets are thumb-sized
11 of 12 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 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 282 words of copy
The homepage carries about 282 words of visible text.
7 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Call Us Speak with our team right away”.
5 calls to action
The homepage has 5 calls to action, for example “BOOK AN APPOINTMENT”, “Call Us Speak with our team right away” and “LEARN MORE”.
4 short forms
4 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Analytics.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Opening hours shown
Your opening hours are on the homepage.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Pinterest Tag and 2 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.
23 cookies set on arrival
23Opening the homepage sets 23 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.
33 other companies contacted
Loading the homepage contacts 33 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 johnnydangandco.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 16 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Swift Speed Optimize · Judge Me Reviews · Inbox · Vo Product Options · Wishlist By Square · Vitals · Pagefly Ai Page Builder · Swift Theme App Extension · Booking · Forms · Pushowl · herokuapp.com · perfectapps.io · kxcdn.com · avada.io · nice-team.net
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 Analytics
- Hosting
- Shopify
Company
- Headquarters
- Houston
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 36 issues on johnnydangandco.com, including 17 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.