target.com website review

targetimg1.com costs a phone 3.2 s of main-thread work and 1.8 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.

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

px-cloud.net costs a phone 1.8 s of main-thread work and 593 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.

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

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

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

8 third-party services load with your homepage (targetimg1.com, px-cloud.net and crcldu.com and others), adding 3.8 MB and 7.3 s of main-thread time.

About 1.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.

crcldu.com costs a phone 809 ms of main-thread work and 257 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.

26 images could be 822 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

px-cdn.net costs a phone 712 ms of main-thread work and 272 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.

Google/Doubleclick Ads costs a phone 536 ms of main-thread work and 673 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 block the main thread while loading, the longest for 551 ms. During a long task the page ignores taps.

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

About 29 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.

9 KiB could be saved by minifying JavaScript.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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.

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

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

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

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

Your largest element takes 7.5 s to render on a phone. Google's threshold for “good” is 2.5 s.

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

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

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

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

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

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

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

Your homepage downloads 12.5 MB in 341 requests on a phone: media 6.5 MB (3), scripts 4.1 MB (111) and images 1.2 MB (51). Under 2 MB keeps phones on slow connections fast.

GUEST_3829059e-79ae-486b-8157-b62d5ccaa301 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).

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

Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

1 frame has no title, so screen-reader users cannot tell what it contains.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Users should be able to zoom and scale the text up to 500%: 1 element on the page fails this check, rated minor by axe-core.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

The homepage links to 63 pages on target.com and 1 external page.

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.

/c/shop-all-categories/-/N-5xsxf, /c/top-deals/-/N-4xw74, /c/order-pickup/-/N-ng0a0, /c/halloween/-/N-5xt2o, /pl/195113812 and /c/halloween-party-supplies/-/N-4y6xj and 3 others have no <title>, so Google invents the link text in results.

/circlecard, /weekly-ad, /c/shop-all-categories/-/N-5xsxf, /c/top-deals/-/N-4xw74, /c/order-pickup/-/N-ng0a0 and /c/halloween/-/N-5xt2o and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

/gift-registry, /c/shop-all-categories/-/N-5xsxf, /c/top-deals/-/N-4xw74, /c/order-pickup/-/N-ng0a0, /c/halloween/-/N-5xt2o and /pl/195113812 and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

/gift-registry, /c/shop-all-categories/-/N-5xsxf, /c/top-deals/-/N-4xw74, /c/order-pickup/-/N-ng0a0, /c/halloween/-/N-5xt2o and /pl/195113812 and 4 others have 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.

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

3 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

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 401 ()”.

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

Large scripts ship without source maps.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 554 words of visible text.

Before a visitor clicks anything, the page loads FullStory, Google Ads 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.

Opening the homepage sets 41 cookies (measured from a US location before any click).

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.

Loading the homepage contacts 33 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.