Website review, no card needed
palmbeachautographs.com website review
Visit site (opens in a new tab)Reviewed 8 November 202649 issues · 98 checks
This review found 49 issues worth fixing on palmbeachautographs.com, 19 of them high impact, across 98 checks. The most urgent: render-blocking requests. 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
80B- #48,879 of 125,770 reviewed websitesbeats 55%
- #32,112 of 70,261 online storesbeats 48%
- #30,840 of 63,823 Shopify storesbeats 45%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.0 s |
| May 23, 2026 | 1.8 s |
| May 30, 2026 | 1.6 s |
| Jun 6, 2026 | 1.6 s |
| Jun 13, 2026 | 1.7 s |
| Jun 20, 2026 | 1.8 s |
| Jun 27, 2026 | 1.8 s |
| Jul 4, 2026 | 1.8 s |
| Jul 11, 2026 | 1.8 s |
| Jul 18, 2026 | 1.9 s |
| Jul 25, 2026 | 1.9 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 | 1.9 s |
| Sep 5, 2026 | 1.9 s |
| Sep 12, 2026 | 1.7 s |
| Sep 19, 2026 | 1.7 s |
| Sep 26, 2026 | 1.7 s |
| Oct 3, 2026 | 1.8 s |
| Oct 10, 2026 | 2.1 s |
| Oct 17, 2026 | 2.1 s |
| Oct 24, 2026 | 2.0 s |
| Oct 31, 2026 | 2.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 90 ms |
| May 23, 2026 | 87 ms |
| May 30, 2026 | 88 ms |
| Jun 6, 2026 | 88 ms |
| Jun 13, 2026 | 88 ms |
| Jun 20, 2026 | 95 ms |
| Jun 27, 2026 | 95 ms |
| Jul 4, 2026 | 96 ms |
| Jul 11, 2026 | 95 ms |
| Jul 18, 2026 | 95 ms |
| Jul 25, 2026 | 96 ms |
| Aug 1, 2026 | 96 ms |
| Aug 8, 2026 | 100 ms |
| Aug 15, 2026 | 102 ms |
| Aug 22, 2026 | 99 ms |
| Aug 29, 2026 | 99 ms |
| Sep 5, 2026 | 97 ms |
| Sep 12, 2026 | 96 ms |
| Sep 19, 2026 | 103 ms |
| Sep 26, 2026 | 104 ms |
| Oct 3, 2026 | 104 ms |
| Oct 10, 2026 | 111 ms |
| Oct 17, 2026 | 106 ms |
| Oct 24, 2026 | 112 ms |
| Oct 31, 2026 | 114 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.6 s
1.1 s
1.7 s
2.3 s
2.9 s
3.4 s
4.0 s
4.6 s
Speed
Render-blocking requests
2.1 s18 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.1 s.
Shopify adds 1.1 s
1.1 sShopify costs a phone 1.1 s of main-thread work and 1.2 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.
Main-thread work: 5.2 s
A phone's processor spends 5.2 s on main-thread work while loading, 2.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3,731 HTML elements
The page has 3,731 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
2.2 MB22 images could be 2.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, pop-convert.com and reddit and others), adding 1.9 MB and 1.6 s of main-thread time.
Mobile performance score: 71
71/100Your mobile performance score is 71. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
260 ms · 439 KiBAbout 439 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 260 ms faster on a phone.
Reduce unused CSS
150 ms · 118 KiBAbout 118 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
217 KiB11 files are served with short cache lifetimes, so returning visitors download them again (217 KiB).
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 158 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Duplicated JavaScript
35 KiB35 KiB JavaScript is shipped twice across bundles.
Legacy JavaScript
30 KiBPolyfills for old browsers add 30 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: 20 ms
20 msYour server sent the HTML in 20 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.
Time to Interactive: 20.1 s
20.1 sThe page becomes fully interactive after 20.1 s. Good is under 3.8 s.
Speed Index: 11.7 s
11.7 sVisually, the page fills in at 11.7 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.2 s
3.2 sThe first text or image appears after 3.2 s on a phone. Good is under 1.8 s.
Real-user CLS: 0.13
0.13For real visitors the layout shifts by 0.13 (75th percentile). Good is under 0.1.
Tap response (INP) got 28% slower for real visitors
+28%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 90 ms to 114 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest Contentful Paint: 3.2 s
3.2 sYour largest element takes 3.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “View All Live Signing Events”.
Cumulative Layout Shift: 0.114
0.114The layout shifts by 0.114 while loading, so content jumps under the reader's thumb. Good is under 0.1.
9 images without width and height
9 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
+9%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.0 s to 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 1.7 s
1.7 sReal visitors wait 1.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 154 ms
154 msReal visitors wait 154 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.6 s
1.6 sReal visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 577 ms
577 msReal visitors wait 577 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 197 ms
197 msScripts block the page for only 197 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 15.2 MB in 424 requests
15.2 MBYour homepage downloads 15.2 MB in 424 requests on a phone: images 11.6 MB (98), scripts 1.5 MB (136) and other files 953 KiB (129). Under 2 MB keeps phones on slow connections fast.
15 images far larger than shown
3.1 MB15 images are downloaded at several times the size a phone draws them, for example DSC09873.jpg at 3,600 px wide, shown at 300 px. Resized copies would save about 3.1 MB.
1 image over 500 KB
DSC09873.jpg weighs 790 KiB. On a phone connection a single image that size takes seconds.
14 images below the first screen load straight away
14 images further down the page (3.5 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
1 image in older formats
1 image (331 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 4.3 g of CO₂ per visit
4.32 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.32 g of CO₂e: 518.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Invalid ARIA attributes
6 elements use ARIA attributes their role does not allow, which confuses screen readers.
2 buttons without a name
2 buttons have no accessible name, so screen readers announce just “button”.
43 text elements with low contrast
43 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Positive tabindex
24 elements have a tabindex above 0, which scrambles the keyboard order.
3 tap targets too small
3 tap targets are too small or too close together to hit reliably with a finger.
Hidden but focusable
1 element hidden from screen readers can still receive keyboard focus.
21 images without alt text
21 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (10 elements)
All page content should be contained by landmarks: 10 elements on the page fail this check, rated moderate by axe-core.
Document should not have more than one banner landmark (1 element)
Document should not have more than one banner landmark: 1 element on the page fails 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.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
15 links without text
15 visible links have no text or label, so screen readers cannot say where they go.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
ARIA role should be appropriate for the element (6 elements)
ARIA role should be appropriate for the element: 6 elements on the page fail this check, rated minor by axe-core.
Alternative text of images should not be repeated as text (3 elements)
Alternative text of images should not be repeated as text: 3 elements on the page fail this check, rated minor by axe-core.
Headings should not be empty (2 elements)
Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h4, h1 → h3 and h2 → h4), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
1 checks passed
49 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 65 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 16 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (87 characters)
Your title is 87 characters, so Google will cut it off around 60: “Authentic Sports Memorabilia & Live Signings | Florida & TN – Palm Beach Autographs LLC”.
5 H1 headlines
There are 5 <h1> headlines (“MLB”, “Today's top picks” and “”). One clear main headline is easier for people and search engines.
Meta description is long (190 characters)
Your meta description is 190 characters; Google truncates after about 160, so the end of your pitch is cut.
553 internal links, 18 external
The homepage links to 553 pages on palmbeachautographs.com and 18 external pages.
5 checks passed
Canonical URL set
The canonical URL is https://www.palmbeachautographs.com/.
Structured data in place
Structured data found: SocialMediaPosting.
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://www.palmbeachautographs.com/sitemap.xml.
AI search readiness
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.
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,742 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without a meta description
https://www.palmbeachautographs.com/pages/locations has no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://www.palmbeachautographs.com/collections/signings has no <h1> headline, so visitors and search engines get no clear main topic.
3 pages slow to respond
https://www.palmbeachautographs.com/collections/nfl-cincinnati-bengals, https://www.palmbeachautographs.com/collections/nfl-dallas-cowboys and https://www.palmbeachautographs.com/collections/nfl-denver-broncos took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 196 found) and read each the way a search engine does.
5 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.
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
8 small tap targets
8 of 34 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “SearchForm is not defined”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
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.
About 1,371 words of copy
The homepage carries about 1,371 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
8 checks passed
88 calls to action
The homepage has 88 calls to action, for example “Shop Now”, “SHOP NOW” and “SHOP ALL TOP DEALS”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 16 testimonial or review blocks, 2 trust badges and “2303+ reviews”.
Analytics in place
Analytics detected: HubSpot.
Direct contact links
Visitors can reach you directly: 6 phone links 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.
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, HubSpot 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.
22 cookies set on arrival
22Opening the homepage sets 22 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.
52 other companies contacted
Loading the homepage contacts 52 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 palmbeachautographs.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 14 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Froonze Loyalty Wishlist · Klaviyo Email Marketing Sms · Ecomposer Builder · Judge Me Reviews · Rapid Search Bar Filter · Buddha Mega Menu Navigation · Froonze App · Pop Convert · Multivariants · Avada Faqs · Selleasy · Countdown Timer · Easify Product Options · Hulk Product Options
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
- Framework
- jQuery
- 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 49 issues on palmbeachautographs.com, including 17 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.