Website review, no card needed

boscovs.com logo

boscovs.com website review

Visit site (opens in a new tab)Reviewed 11 October 202649 issues · 87 checks

This review found 49 issues worth fixing on boscovs.com, 22 of them high impact, across 87 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
1.8 s1.5 sApr 18Oct 31.8 s
Show as table
DateReal-visitor load time (LCP)
Apr 18, 20261.6 s
Apr 25, 20261.6 s
May 2, 20261.6 s
May 9, 20261.6 s
May 16, 20261.6 s
May 23, 20261.6 s
May 30, 20261.6 s
Jun 6, 20261.6 s
Jun 13, 20261.6 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.8 s
Sep 26, 20261.8 s
Oct 3, 20261.8 s
Real-visitor tap response (INP)75th percentile, phones
269 ms178 msApr 18Oct 3219 ms
Show as table
DateReal-visitor tap response (INP)
Apr 18, 2026237 ms
Apr 25, 2026245 ms
May 2, 2026253 ms
May 9, 2026258 ms
May 16, 2026253 ms
May 23, 2026230 ms
May 30, 2026208 ms
Jun 6, 2026197 ms
Jun 13, 2026188 ms
Jun 20, 2026189 ms
Jun 27, 2026197 ms
Jul 4, 2026201 ms
Jul 11, 2026202 ms
Jul 18, 2026202 ms
Jul 25, 2026201 ms
Aug 1, 2026202 ms
Aug 8, 2026206 ms
Aug 15, 2026211 ms
Aug 22, 2026214 ms
Aug 29, 2026217 ms
Sep 5, 2026218 ms
Sep 12, 2026218 ms
Sep 19, 2026219 ms
Sep 26, 2026219 ms
Oct 3, 2026219 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 boscovs.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. boscovs.com at 0.8 s0.8 s
  2. boscovs.com at 1.6 s1.6 s
  3. boscovs.com at 2.4 s2.4 s
  4. boscovs.com at 3.1 s3.1 s
  5. boscovs.com at 3.9 s3.9 s
  6. boscovs.com at 4.7 s4.7 s
  7. boscovs.com at 5.5 s5.5 s
  8. boscovs.com at 6.3 s6.3 s

Speed

15 to fix15
  • Reduce unused JavaScript

    1.9 s · 784 KiB

    About 784 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.9 s faster on a phone.

  • Use efficient cache lifetimes

    1.8 s · 840 KiB

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

  • audioeye.com adds 2.3 s

    2.3 s

    audioeye.com costs a phone 2.3 s of main-thread work and 385 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.

  • Render-blocking requests

    1.1 s

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

  • Mobile performance score: 15

    15/100

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

  • Main-thread work: 7.8 s

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

  • 4,686 HTML elements

    The page has 4,686 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 (audioeye.com, iovation and Facebook and others), adding 1.6 MB and 3.6 s of main-thread time.

  • Improve image delivery

    450 ms · 2.3 MB

    48 images could be 2.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.

  • Reduce unused CSS

    600 ms · 146 KiB

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

  • Minify JavaScript

    450 ms · 105 KiB

    105 KiB could be saved by minifying JavaScript.

  • 17 long tasks on the main thread

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

  • Facebook adds 252 ms

    252 ms

    Facebook costs a phone 252 ms of main-thread work and 252 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.

  • iovation adds 255 ms

    255 ms

    iovation costs a phone 255 ms of main-thread work and 30 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.

  • Monetate adds 187 ms

    187 ms

    Monetate costs a phone 187 ms of main-thread work and 575 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.

  • Legacy JavaScript

    100 ms · 110 KiB

    Polyfills for old browsers add 110 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 100 ms faster on a phone.

  • Font display

    50 ms

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

1 checks passed
  • Server response: 9 ms

    9 ms

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

Core Web Vitals

10 to fix67
  • 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: 19.7 s

    19.7 s

    Your largest element takes 19.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Fall Festival Extra 15% Off”.

  • Time to Interactive: 29.9 s

    29.9 s

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

  • First Contentful Paint: 6.8 s

    6.8 s

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

  • Cumulative Layout Shift: 0.993

    0.993

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

  • Speed Index: 13.4 s

    13.4 s

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

  • Total Blocking Time: 611 ms

    611 ms

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

  • Real-user CLS: 0.16

    0.16

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

  • Real-user TTFB: 833 ms

    833 ms

    Real visitors wait 833 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • 27 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -9%

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

  • Largest content (LCP) held steady for real visitors

    +9%

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

3 checks passed
  • Real-user LCP: 2.0 s

    2.0 s

    Real visitors wait 2.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 195 ms

    195 ms

    Real visitors wait 195 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user FCP: 1.5 s

    1.5 s

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

Images and page weight

4 to fix43
  • Page weight: 6.0 MB in 259 requests

    6.0 MB

    Your homepage downloads 6.0 MB in 259 requests on a phone: images 3.2 MB (86), scripts 2.2 MB (72) and other files 260 KiB (82). Under 2 MB keeps phones on slow connections fast.

  • 11 images far larger than shown

    1,005 KiB

    11 images are downloaded at several times the size a phone draws them, for example 632247027116109.jpg at 1,200 px wide, shown at 102 px. Resized copies would save about 1,005 KiB.

  • 21 images below the first screen load straight away

    21 images further down the page (1.4 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • An image on the first screen is lazy-loaded

    54bf2de9-1832-4410-b8be-e709eb99af0b 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).

  • 2 images in older formats

    2 images (100 KiB) are 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 1.7 g of CO₂ per visit

    1.69 g

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

Accessibility

6 to fixGoogle 8391
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 2 images without alt text

    2 images have no alt text, which hurts accessibility and image search.

  • Invalid ARIA attributes

    1 element use ARIA attributes their role does not allow, which confuses screen readers.

  • [role]s do not have all required [aria-*] attributes

    [role]s do not have all required [aria-*] attributes (1 element).

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

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

  • 29 links without text

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

  • 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
  • 51 automated accessibility rules passed

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

SEO

7 to fixGoogle 7772
  • No H1 headline

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

  • Title is long (77 characters)

    Your title is 77 characters, so Google will cut it off around 60: “Boscov's Online & In-Store: Clothes, Shoes, Home, Bed, Toys & More - Boscov's”.

  • 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:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 16 links crawlers can't follow

    16 links have no real href, so search engines can't follow them.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

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

  • No X (Twitter) card tag

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

  • 1,149 internal links, 29 external

    The homepage links to 1,149 pages on boscovs.com and 29 external pages.

4 checks passed
  • Meta description: 157 characters

    Your meta description is 157 characters: “Shop Boscovs.com for great values on Apparel and Shoes for the entire family, Handbags, Cosmetics, Jewelry, Domestics, …”.

  • Canonical URL set

    The canonical URL is https://www.boscovs.com/home.

  • 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.boscovs.com/sitemap.xml.

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://www.boscovs.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 (3,563 words), so crawlers that don't run JavaScript still read it.

Other pages

100
  • 15 internal pages checked

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

1 checks passed
  • Linked pages load

    10 pages of 15 loaded without an error (the rest turned automated requests away).

Best practices

4 to fixGoogle 6570
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=5521818&tm=gtm002&Ver=2&mid=d460ab48-771f-4ad6-990e-41563144ef14&bo=1&sid=30fdfef0c5cc11f1a3db67e71630cba4&vid=30fe1300c5cc11f1bed98fe88982562c&vids=1&msclkid=N&pi=918.

  • 17 small tap targets

    17 of 36 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 406 ()”.

  • Requests the geolocation permission on page load

    Requests the geolocation permission on page load.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix92
  • Thin social proof

    Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

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

    The homepage carries about 309 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 Now” and “Track My Order”.

  • 30 calls to action

    The homepage has 30 calls to action, for example “Shop Now”, “Menu Created with Sketch Beta. Shop” and “Track My Order”.

  • 5 short forms

    5 short forms (6 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager and Microsoft Clarity.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 0 email links.

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

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

  • 31 cookies set on arrival

    31

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

  • 49 other companies contacted

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 49 issues on boscovs.com, including 25 speed issues, 7 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

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