Website review, no card needed
beallsflorida.com website review
Visit site (opens in a new tab)Reviewed 1 November 202635 issues · 85 checks
This review found 35 issues worth fixing on beallsflorida.com, 17 of them high impact, across 85 checks. The most urgent: use efficient cache lifetimes. 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
68D- #105,933 of 120,620 reviewed websitesbeats 10%
- #63,659 of 68,290 online storesbeats 5%
- #771 of 889 BigCommerce storesbeats 10%
Closest competitors among BigCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.2 s |
| May 16, 2026 | 2.1 s |
| May 23, 2026 | 2.1 s |
| May 30, 2026 | 2.0 s |
| Jun 6, 2026 | 2.1 s |
| Jun 13, 2026 | 2.1 s |
| Jun 20, 2026 | 2.1 s |
| Jun 27, 2026 | 2.1 s |
| Jul 4, 2026 | 2.1 s |
| Jul 11, 2026 | 2.2 s |
| Jul 18, 2026 | 2.2 s |
| Jul 25, 2026 | 2.3 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.6 s |
| Sep 5, 2026 | 2.6 s |
| Sep 12, 2026 | 2.8 s |
| Sep 19, 2026 | 2.8 s |
| Sep 26, 2026 | 2.9 s |
| Oct 3, 2026 | 2.8 s |
| Oct 10, 2026 | 2.6 s |
| Oct 17, 2026 | 2.4 s |
| Oct 24, 2026 | 2.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 328 ms |
| May 16, 2026 | 327 ms |
| May 23, 2026 | 322 ms |
| May 30, 2026 | 320 ms |
| Jun 6, 2026 | 322 ms |
| Jun 13, 2026 | 324 ms |
| Jun 20, 2026 | 331 ms |
| Jun 27, 2026 | 336 ms |
| Jul 4, 2026 | 329 ms |
| Jul 11, 2026 | 325 ms |
| Jul 18, 2026 | 317 ms |
| Jul 25, 2026 | 313 ms |
| Aug 1, 2026 | 311 ms |
| Aug 8, 2026 | 312 ms |
| Aug 15, 2026 | 312 ms |
| Aug 22, 2026 | 313 ms |
| Aug 29, 2026 | 315 ms |
| Sep 5, 2026 | 320 ms |
| Sep 12, 2026 | 322 ms |
| Sep 19, 2026 | 328 ms |
| Sep 26, 2026 | 329 ms |
| Oct 3, 2026 | 328 ms |
| Oct 10, 2026 | 326 ms |
| Oct 17, 2026 | 321 ms |
| Oct 24, 2026 | 321 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
1.2 s
2.3 s
3.5 s
4.7 s
5.9 s
7.0 s
8.2 s
9.4 s
Speed
Use efficient cache lifetimes
2.3 s · 1.9 MB139 files are served with short cache lifetimes, so returning visitors download them again (1.9 MB).
Render-blocking requests
1.4 s7 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.
Google Tag Manager adds 1.1 s
1.1 sGoogle Tag Manager costs a phone 1.1 s of main-thread work and 856 KiB 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: 10.7 s
A phone's processor spends 10.7 s on main-thread work while loading, 4.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 25
25/100Your mobile performance score is 25. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
3,913 HTML elements
The page has 3,913 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 (Google Tag Manager, Google CDN and Listrak and others), adding 2.2 MB and 2.3 s of main-thread time.
Reduce unused JavaScript
2.2 MBAbout 2.2 MB of JavaScript is downloaded but never used on this page.
Reduce unused CSS
610 ms · 205 KiBAbout 205 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 610 ms faster on a phone.
Improve image delivery
350 ms · 446 KiB34 images could be 446 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.
Google CDN adds 572 ms
572 msGoogle CDN costs a phone 572 ms of main-thread work and 776 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 277 ms. During a long task the page ignores taps.
Minify JavaScript
139 KiB139 KiB could be saved by minifying JavaScript.
Font display
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
Legacy JavaScript
39 KiBPolyfills for old browsers add 39 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: 35 ms
35 msYour server sent the HTML in 35 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: 27.2 s
27.2 sThe page becomes fully interactive after 27.2 s. Good is under 3.8 s.
Largest Contentful Paint: 7.3 s
7.3 sYour largest element takes 7.3 s to render on a phone. Google's threshold for “good” is 2.5 s.
Total Blocking Time: 2.2 s
2.2 sScripts block taps and scrolling for 2.2 s in total while the page loads. Good is under 200 ms.
Speed Index: 8.1 s
8.1 sVisually, the page fills in at 8.1 s (Speed Index). Good is under 3.4 s.
Cumulative Layout Shift: 0.263
0.263The layout shifts by 0.263 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Real-user INP: 302 ms
302 msReal visitors wait 302 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.18
0.18For real visitors the layout shifts by 0.18 (75th percentile). Good is under 0.1.
24 images without width and height
24 images have no width and height attributes, so the layout jumps as each one loads.
First Contentful Paint: 2.0 s
2.0 sThe first text or image appears after 2.0 s on a phone. Good is under 1.8 s.
Tap response (INP) held steady for real visitors
-2%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 328 ms to 321 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 10% slower for real visitors
+10%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.2 s to 2.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 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 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: 529 ms
529 msReal visitors wait 529 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
Page weight: 5.9 MB in 263 requests
5.9 MBYour homepage downloads 5.9 MB in 263 requests on a phone: scripts 2.5 MB (59), images 1.8 MB (143) and other files 1.0 MB (39). Under 2 MB keeps phones on slow connections fast.
9 images below the first screen load straight away
9 images further down the page (286 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.7 g of CO₂ per visit
1.67 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.67 g of CO₂e: 200.1 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
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
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.
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
Headings skip levels
Headings skip levels (h2 → h5), 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).
2 checks passed
Every image has alt text
All 59 images in the HTML carry an alt attribute.
51 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 3 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
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.
2 links with vague text
2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
510 internal links, 16 external
The homepage links to 510 pages on beallsflorida.com and 16 external pages.
6 checks passed
Meta description: 148 characters
Your meta description is 148 characters: “Shop Bealls Florida for clothing, shoes, home décor, and gifts. Discover relaxed coastal style, great value, and easy s…”.
Title: 58 characters
Your title is a healthy 58 characters: “Bealls Florida | Clothing, Shoes & Home with Coastal Style”.
Canonical URL set
The canonical URL is https://www.beallsflorida.com/.
Structured data in place
Structured data found: Organization and WebPage.
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.beallsflorida.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.beallsflorida.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.
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.
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,462 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without a title
https://www.beallsflorida.com/promotion-disclaimers has no <title>, so Google invents the link text in results.
1 page points its canonical at the homepage
https://www.beallsflorida.com/track-order-status declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.
5 pages without a meta description
https://www.beallsflorida.com/promotion-disclaimers, https://www.beallsflorida.com/shipping-delivery, https://www.beallsflorida.com/c/seasonal, https://www.beallsflorida.com/c/seasonal/harvest and https://www.beallsflorida.com/c/seasonal/harvest/home 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 196 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.
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.
Best practices
4 low-resolution images
4 images are served at too low a resolution for sharp phone screens.
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
54 of 58 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.
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 698 words of copy
The homepage carries about 698 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop with AI” and “Shop”.
15 calls to action
The homepage has 15 calls to action, for example “Shop with AI”, “Shop” and “Golf Shop”.
11 short forms
11 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (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.
8 cookies set on arrival
8Opening the homepage sets 8 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.
18 other companies contacted
Loading the homepage contacts 18 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 beallsflorida.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
- Next.js
- E-commerce
- BigCommerce
- Analytics
- Google Tag Manager
- Hosting
- Vercel
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 35 issues on beallsflorida.com, including 22 speed issues, 4 SEO issues and 1 conversion gap. 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.