Website review, no card needed

glamour.com logo

glamour.com website review

Visit site (opens in a new tab)Reviewed 17 November 202640 issues · 94 checks

This review found 40 issues worth fixing on glamour.com, 13 of them high impact, across 94 checks. The most urgent: main-thread work: 16.4 s. 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.9 s1.3 sMay 30Nov 141.6 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.5 s
Jun 6, 20261.5 s
Jun 13, 20261.5 s
Jun 20, 20261.4 s
Jun 27, 20261.4 s
Jul 4, 20261.4 s
Jul 11, 20261.4 s
Jul 18, 20261.6 s
Jul 25, 20261.7 s
Aug 1, 20261.7 s
Aug 8, 20261.7 s
Aug 15, 20261.8 s
Aug 22, 20261.8 s
Aug 29, 20261.8 s
Sep 5, 20261.8 s
Sep 12, 20261.8 s
Sep 19, 20261.7 s
Sep 26, 20261.7 s
Oct 3, 20261.7 s
Oct 10, 20261.7 s
Oct 17, 20261.7 s
Oct 24, 20261.8 s
Oct 31, 20261.9 s
Nov 7, 20261.7 s
Nov 14, 20261.6 s
Real-visitor tap response (INP)75th percentile, phones
262 ms186 msMay 30Nov 14204 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026228 ms
Jun 6, 2026229 ms
Jun 13, 2026232 ms
Jun 20, 2026228 ms
Jun 27, 2026224 ms
Jul 4, 2026222 ms
Jul 11, 2026224 ms
Jul 18, 2026238 ms
Jul 25, 2026253 ms
Aug 1, 2026253 ms
Aug 8, 2026245 ms
Aug 15, 2026222 ms
Aug 22, 2026213 ms
Aug 29, 2026204 ms
Sep 5, 2026201 ms
Sep 12, 2026197 ms
Sep 19, 2026197 ms
Sep 26, 2026199 ms
Oct 3, 2026195 ms
Oct 10, 2026197 ms
Oct 17, 2026195 ms
Oct 24, 2026197 ms
Oct 31, 2026202 ms
Nov 7, 2026203 ms
Nov 14, 2026204 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 glamour.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. glamour.com at 3.4 s3.4 s
  2. glamour.com at 6.9 s6.9 s
  3. glamour.com at 10.3 s10.3 s
  4. glamour.com at 13.7 s13.7 s
  5. glamour.com at 17.2 s17.2 s
  6. glamour.com at 20.6 s20.6 s
  7. glamour.com at 24.0 s24.0 s
  8. glamour.com at 27.4 s27.4 s

Speed

14 to fix31
  • Main-thread work: 16.4 s

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

  • Google Tag Manager adds 1.3 s

    1.3 s

    Google Tag Manager costs a phone 1.3 s of main-thread work and 966 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.

  • Mobile performance score: 31

    31/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Integral Ad Science and Google/Doubleclick Ads and others), adding 4.5 MB and 4.5 s of main-thread time.

  • Use efficient cache lifetimes

    800 ms · 2.6 MB

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

  • Reduce unused JavaScript

    2.0 MB

    About 2.0 MB of JavaScript is downloaded but never used on this page.

  • Google/Doubleclick Ads adds 890 ms

    890 ms

    Google/Doubleclick Ads costs a phone 890 ms of main-thread work and 1.8 MB 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.

  • Integral Ad Science adds 956 ms

    956 ms

    Integral Ad Science costs a phone 956 ms of main-thread work and 454 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 896 ms. During a long task the page ignores taps.

  • Improve image delivery

    522 KiB

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

  • DoubleVerify adds 343 ms

    343 ms

    DoubleVerify costs a phone 343 ms of main-thread work and 107 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.

  • permutive.app adds 293 ms

    293 ms

    permutive.app costs a phone 293 ms of main-thread work and 525 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.

  • Reduce unused CSS

    330 KiB

    About 330 KiB of CSS is downloaded but never applied on this page.

  • 1,750 HTML elements

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

  • Legacy JavaScript

    20 KiB

    Polyfills for old browsers add 20 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.

  • Minify CSS

    5 KiB

    5 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 27 ms

    27 ms

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

Core Web Vitals

6 to fix100
  • Speed Index: 28.8 s

    28.8 s

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

  • Time to Interactive: 62.0 s

    62.0 s

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

  • Total Blocking Time: 4.1 s

    4.1 s

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

  • Largest Contentful Paint: 7.7 s

    7.7 s

    Your largest element takes 7.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “20 Toasty Gifts for the Friend Who’s Always Freezing”.

  • 31 images without width and height

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

  • Cumulative Layout Shift: 0.12

    0.12

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

  • Largest content (LCP) got 11% slower for real visitors

    +11%

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

8 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.6 s

    1.6 s

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

  • Real-user INP: 186 ms

    186 ms

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

  • Real-user CLS: 0.01

    0.01

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

  • Real-user FCP: 1.2 s

    1.2 s

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

  • Real-user TTFB: 661 ms

    661 ms

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

  • Tap response (INP) got 11% faster for real visitors

    -11%

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

  • First Contentful Paint: 1.7 s

    1.7 s

    The first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.

Images and page weight

1 to fix70
  • Page weight: 11.9 MB in 632 requests

    11.9 MB

    Your homepage downloads 11.9 MB in 632 requests on a phone: scripts 5.4 MB (105), media 2.3 MB (1) and images 1.6 MB (173). Under 2 MB keeps phones on slow connections fast.

  • About 3.4 g of CO₂ per visit

    3.37 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

7 to fixGoogle 8992
  • Interactive controls must not be nested (28 elements)

    Interactive controls must not be nested: 28 elements on the page fail this check, rated serious by axe-core.

  • 8 tap targets too small

    8 tap targets are too small or too close together to hit reliably with a finger.

  • Elements must only use permitted ARIA attributes (1 element)

    Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious 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.

  • 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 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Headings skip levels

    Headings skip levels (h1 → h3 and h3 → h6), 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 36 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 59 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 8 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 9293
  • Title is long (71 characters)

    Your title is 71 characters, so Google will cut it off around 60: “Women's Issues, Politics, Fashion, Beauty, Entertainment News | Glamour”.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 97 internal links, 24 external

    The homepage links to 97 pages on glamour.com and 24 external pages.

7 checks passed
  • Meta description: 128 characters

    Your meta description is 128 characters: “Glamour.com is your source for what matters to women now, from outfit ideas and makeup tutorials to celebrity news and …”.

  • One H1 headline

    Your main headline reads: “Glamour”.

  • Canonical URL set

    The canonical URL is https://www.glamour.com/.

  • Structured data in place

    Structured data found: ItemList, Organization and WebSite.

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

AI search readiness

2 to fix53
  • robots.txt blocks 4 AI answer engine crawlers

    4 of 6

    Your robots.txt shuts out Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.

  • Organization data is thin (3 of 6 facts)

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

  • No llms.txt

    There is no https://www.glamour.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.

  • Opted out of AI training for 4 crawlers

    robots.txt blocks ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.

1 checks passed
  • Text is in the HTML

    Your server sends the page's text in the HTML (667 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 1 page without a meta description

    https://www.glamour.com/health-fitness has no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages slow to respond

    https://www.glamour.com/under-200-edit and https://www.glamour.com/gallery/best-gift-ideas-for-women took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

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

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

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

4 to fixGoogle 3574
  • 2 broken images

    2 images failed to load on a phone, for example https://trx-hub.com/i/m/i.png?q=N4IghgLhBOD6BmB7aB3M0AmBLAdgcxAC5gBfAGhAFsBTCMDSMI0AY0Rwmo4EkARIkAFYWAJmoiwg+ABYWABmkA2AOwiW8xQCNBcqSAptEAayzUAwgDkBLeMoAc0gMx3qAWmmbpARnfKMi1zAwaXhA53gvQUcATlF5fRA2AAc.

  • 49 third-party cookies

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

  • Deprecated browser APIs

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

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Access to fetch at 'https://id-mapper-service.gp-prod.conde.digital/associations' from origin 'https://www.glamour.com'…”.

  • Browser-reported issues

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

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

    39 of 40 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix75
  • Thin social proof

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

  • No analytics detected

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

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach 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 597 words of copy

    The homepage carries about 597 words of visible text.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP OUR GIFT HUB” and “BUY NOW”.

  • 5 calls to action

    The homepage has 5 calls to action, for example “Shop Our Gift Hub”, “BUY NOW” and “Sign Up”.

  • 1 short form

    A short form (1 field at most) is right on the homepage, asking for an email.

Privacy and tracking

1 to fix
  • 13 trackers load before any consent

    13

    Before a visitor clicks anything, the page loads Amazon Ads, Comscore, Criteo, Google Ads and Google Analytics and 8 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.

  • 41 cookies set on arrival

    41

    Opening the homepage sets 41 cookies, 2 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.

  • 71 other companies contacted

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

Upkeep, stack and company

Stack

Hosting
AWS

Company

Founded
1939

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 40 issues on glamour.com, including 20 speed issues, 1 SEO issue and 3 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

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