Website review, no card needed

altonlane.com logo

altonlane.com website review

Visit site (opens in a new tab)Reviewed 19 October 202652 issues · 94 checks

This review found 52 issues worth fixing on altonlane.com, 20 of them high impact, across 94 checks. The most urgent: render-blocking requests. 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
4.4 s3.2 sMay 2Oct 174.2 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20263.4 s
May 9, 20263.4 s
May 16, 20263.4 s
May 23, 20263.4 s
May 30, 20263.5 s
Jun 6, 20263.5 s
Jun 13, 20263.4 s
Jun 20, 20263.5 s
Jun 27, 20263.6 s
Jul 4, 20263.5 s
Jul 11, 20263.6 s
Jul 18, 20263.5 s
Jul 25, 20263.4 s
Aug 1, 20263.5 s
Aug 8, 20263.4 s
Aug 15, 20263.4 s
Aug 22, 20263.5 s
Aug 29, 20263.5 s
Sep 5, 20263.6 s
Sep 12, 20263.6 s
Sep 19, 20263.6 s
Sep 26, 20263.7 s
Oct 3, 20263.9 s
Oct 10, 20264.0 s
Oct 17, 20264.2 s
Real-visitor tap response (INP)75th percentile, phones
215 ms174 msMay 2Oct 17196 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026205 ms
May 9, 2026208 ms
May 16, 2026198 ms
May 23, 2026188 ms
May 30, 2026189 ms
Jun 6, 2026187 ms
Jun 13, 2026187 ms
Jun 20, 2026187 ms
Jun 27, 2026189 ms
Jul 4, 2026186 ms
Jul 11, 2026183 ms
Jul 18, 2026183 ms
Jul 25, 2026179 ms
Aug 1, 2026180 ms
Aug 8, 2026187 ms
Aug 15, 2026191 ms
Aug 22, 2026196 ms
Aug 29, 2026205 ms
Sep 5, 2026210 ms
Sep 12, 2026208 ms
Sep 19, 2026200 ms
Sep 26, 2026188 ms
Oct 3, 2026188 ms
Oct 10, 2026191 ms
Oct 17, 2026196 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 altonlane.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. altonlane.com at 2.3 s2.3 s
  2. altonlane.com at 4.7 s4.7 s
  3. altonlane.com at 7.0 s7.0 s
  4. altonlane.com at 9.3 s9.3 s
  5. altonlane.com at 11.6 s11.6 s
  6. altonlane.com at 13.9 s13.9 s
  7. altonlane.com at 16.3 s16.3 s
  8. altonlane.com at 18.6 s18.6 s

Speed

15 to fix0
  • Render-blocking requests

    7.2 s

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

  • Use efficient cache lifetimes

    5.6 s · 1.4 MB

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

  • Reduce unused JavaScript

    3.1 s · 1.4 MB

    About 1.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.1 s faster on a phone.

  • Google Tag Manager adds 2.9 s

    2.9 s

    Google Tag Manager costs a phone 2.9 s of main-thread work and 717 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: 20.9 s

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

  • Reduce unused CSS

    1.4 s · 256 KiB

    About 256 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.4 s faster on a phone.

  • Mobile performance score: 0

    0/100

    Your mobile performance score is 0 (desktop: 24). 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, Facebook and Hubspot and others), adding 2.4 MB and 7.1 s of main-thread time.

  • 20 long tasks on the main thread

    20 long tasks block the main thread while loading, the longest for 1.3 s. During a long task the page ignores taps.

  • Improve image delivery

    1.2 MB

    2 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Facebook adds 902 ms

    902 ms

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

  • Hubspot adds 814 ms

    814 ms

    Hubspot costs a phone 814 ms of main-thread work and 109 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.

  • Klaviyo adds 716 ms

    716 ms

    Klaviyo costs a phone 716 ms of main-thread work and 331 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.

  • Minify JavaScript

    600 ms · 64 KiB

    64 KiB could be saved by minifying JavaScript.

  • ZenDesk adds 607 ms

    607 ms

    ZenDesk costs a phone 607 ms of main-thread work and 413 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.

  • Font display

    250 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 250 ms).

  • Legacy JavaScript

    102 KiB

    Polyfills for old browsers add 102 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: 11 ms

    11 ms

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

Core Web Vitals

12 to fix33
  • 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.

  • Real-user CLS: 1.50

    1.50

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

  • Cumulative Layout Shift: 1.47

    1.47

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

  • First Contentful Paint: 8.0 s

    8.0 s

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

  • Largest Contentful Paint: 12.2 s

    12.2 s

    Your largest element takes 12.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Delivery in 2 Weeks & a 100% Fit Guarantee.”.

  • Speed Index: 21.4 s

    21.4 s

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

  • Total Blocking Time: 8.3 s

    8.3 s

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

  • Time to Interactive: 35.8 s

    35.8 s

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

  • Real-user LCP: 3.9 s

    3.9 s

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

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

    +21%

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

  • Real-user FCP: 2.7 s

    2.7 s

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

  • 23 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -6%

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

2 checks passed
  • Real-user INP: 191 ms

    191 ms

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

  • Real-user TTFB: 592 ms

    592 ms

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

Images and page weight

1 to fix70
  • Page weight: 6.1 MB in 226 requests

    6.1 MB

    Your homepage downloads 6.1 MB in 226 requests on a phone: scripts 3.3 MB (81), images 2.1 MB (55) and stylesheets 285 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • About 1.7 g of CO₂ per visit

    1.74 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.74 g of CO₂e: 208.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

11 to fixGoogle 7985
  • 1 button without a name

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

  • Links look like plain text

    3 links inside paragraphs rely on colour alone to stand out.

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

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

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

  • Document should not have more than one banner landmark (1 element)

    Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

  • Zoom is disabled

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

  • 3 form fields without a label

    3 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • 1 link without text

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

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h1 → h3, h1 → h3 and h1 → h3), which makes the page harder to scan with a screen reader.

1 checks passed
  • 37 automated accessibility rules passed

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

SEO

4 to fixGoogle 9285
  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 6 H1 headlines

    There are 6 <h1> headlines (“FEATURED”, “GET FITTED” and “GROOMSMEN”). One clear main headline is easier for people and search engines.

  • No XML sitemap

    No XML sitemap at https://www.altonlane.com/sitemap.xml, so Google discovers your pages only by following links.

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • 72 internal links, 0 external

    The homepage links to 72 pages on altonlane.com and 0 external pages.

5 checks passed
  • Meta description: 158 characters

    Your meta description is 158 characters: “Customizing men’s tailored suits and tuxedos is easy. Design your custom suit or tux in 2 minutes and get it delivered …”.

  • Title: 56 characters

    Your title is a healthy 56 characters: “Men’s Tailored Suits | Delivered in 2 Weeks | Alton Lane”.

  • Canonical URL set

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

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

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.altonlane.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 (1,438 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix62
  • 1 linked page is broken

    Your homepage links to https://www.altonlane.com/custom-made-tuxedo-pants, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 8 pages share 4 titles

    https://www.altonlane.com/custom-made/suits and https://www.altonlane.com/custom-made/double-breasted-suits all use the title “Custom Suits for Men | Tailored Designs | Shop Alton Lane”, and 3 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 3 pages without a meta description

    https://www.altonlane.com/custom-made/tuxedos, https://www.altonlane.com/custom-made/tuxedo-jackets and https://www.altonlane.com/custom-made/double-breasted-tuxedo-jackets have no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages share a meta description

    https://www.altonlane.com/custom-made/suits and https://www.altonlane.com/custom-made/double-breasted-suits use the same meta description. A description written for each page earns more clicks.

  • 1 page slow to respond

    https://www.altonlane.com/custom-made/tuxedos took over 3 s to send its HTML from our server.

  • 15 internal pages checked

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

4 checks passed
  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • 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 14 pages that loaded have a <title>.

Best practices

2 to fixGoogle 10086
  • Scrolls sideways on phones

    On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.

  • 6 small tap targets

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

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix86
  • Thin social proof

    Social proof on the homepage: 2 testimonial or review blocks. 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.

  • About 946 words of copy

    The homepage carries about 946 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”.

  • 9 calls to action

    The homepage has 9 calls to action, for example “Shop”, “Made to order” and “Shop now”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 1 email link.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

  • 10 trackers load before any consent

    10

    Before a visitor clicks anything, the page loads Amplitude, Google Ads, Google Analytics, Google Tag Manager and HubSpot and 5 mores (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

  • 9 cookies set on arrival

    9

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

  • 27 other companies contacted

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

1 checks passed
  • Consent tool: HubSpot cookie banner

    A consent management tool (HubSpot cookie banner) loads with the page.

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

Upkeep, stack and company

Company

Founded
2009

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 52 issues on altonlane.com, including 27 speed issues, 4 SEO issues and 2 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