chicos.com website review

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

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, ContentSquare and Facebook and others), adding 2.2 MB and 1.2 s of main-thread time.

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

Google Tag Manager costs a phone 483 ms of main-thread work and 858 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 436 ms. During a long task the page ignores taps.

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

ContentSquare costs a phone 299 ms of main-thread work and 199 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.

The page has 1,765 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

Curalate costs a phone 82 ms of main-thread work and 354 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.

audioeye.com costs a phone 48 ms of main-thread work and 323 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.

133 KiB could be saved by minifying JavaScript.

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

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.

Your largest element takes 12.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Flash sale $50 off your $200+ purchase plus 25% off full pr…”.

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

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

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

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

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

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

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

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

Your homepage downloads 6.6 MB in 335 requests on a phone: scripts 4.8 MB (176), images 1.2 MB (32) and other files 256 KiB (96). Under 2 MB keeps phones on slow connections fast.

Hero50OFF_10.12-M.jpg 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 1.88 g of CO₂e: 225.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

16 buttons have no accessible name, so screen readers announce just “button”.

Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.

1 tap target is too small or too close together to hit reliably with a finger.

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 83 pages on chicos.com and 10 external pages.

Your Organization JSON-LD is missing url, logo, sameAs (social profiles) and description. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

/store and / all use the title “Women's Clothing & Apparel Online & In-Store | Chico's”. Search engines can't tell which page to show for a search, so each competes with the others.

/store/page/credit has no meta description, so Google writes the search snippet from whatever text it finds.

/, /store/category/sale/catsaleschicos, /store/category/limited-time-offer/cat37949281 and /store/order-lookup use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example /, whose canonical is /store. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/, /store/category/sale/catsaleschicos, /store/category/limited-time-offer/cat37949281, /store/order-lookup, /store/category/clothing/cat11199290 and /store/category/shoes-accessories/cat14609299 and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.

/store/order-lookup 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.

/locations took over 3 s to send its HTML from our server.

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

16 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 is set on load; browsers are restricting these, so whatever relies on them breaks.

2 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'carousels')”.

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

Large scripts ship without source maps.

1 link to other sites is dead, for example http://www.chicosfas.com/ (404).

Opening https://chicos.com goes through 2 redirects before the homepage loads.

4 links go through two or more redirects, for example https://www.chicos.com/store/category/dresses+skirts/cat40004/?_ics=1706808620672&irclickid=~14YOIHLHywmrszFKIJPWMDEGIORSNVSNRJzGHxypmi~2YWLJFvri.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

chicos.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

chicos.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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 1,027 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

DMARC is set to p=none, so mail pretending to be chicos.com is still delivered. Add a report address, check the reports, then move to quarantine.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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

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