Website review, no card needed

alexlee.com logo

alexlee.com website review

Visit site (opens in a new tab)Reviewed 19 October 202634 issues · 82 checks

This review found 34 issues worth fixing on alexlee.com, 10 of them high impact, across 82 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
2.2 s1.7 sApr 25Oct 102.1 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20261.8 s
May 2, 20261.8 s
May 9, 20261.9 s
May 16, 20261.8 s
May 23, 20261.9 s
May 30, 20262.0 s
Jun 6, 20262.0 s
Jun 13, 20262.2 s
Jun 20, 20262.0 s
Jun 27, 20262.0 s
Jul 4, 20262.0 s
Jul 11, 20262.0 s
Jul 18, 20261.9 s
Jul 25, 20261.9 s
Aug 1, 20261.9 s
Aug 8, 20261.9 s
Aug 15, 20261.9 s
Aug 22, 20261.9 s
Aug 29, 20261.8 s
Sep 5, 20261.8 s
Sep 12, 20261.8 s
Sep 19, 20261.9 s
Sep 26, 20262.0 s
Oct 3, 20262.1 s
Oct 10, 20262.1 s
Real-visitor tap response (INP)75th percentile, phones
71 ms61 msApr 25Oct 1070 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 202662 ms
May 2, 202662 ms
May 9, 202662 ms
May 16, 202662 ms
May 23, 202662 ms
May 30, 202664 ms
Jun 6, 202664 ms
Jun 13, 202664 ms
Jun 20, 202664 ms
Jun 27, 202663 ms
Jul 4, 202663 ms
Jul 11, 202663 ms
Jul 18, 202663 ms
Jul 25, 202663 ms
Aug 1, 202663 ms
Aug 8, 202664 ms
Aug 15, 202668 ms
Aug 22, 202668 ms
Aug 29, 202667 ms
Sep 5, 202664 ms
Sep 12, 202662 ms
Sep 19, 202665 ms
Sep 26, 202668 ms
Oct 3, 202670 ms
Oct 10, 202670 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 alexlee.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. alexlee.com at 0.4 s0.4 s
  2. alexlee.com at 0.8 s0.8 s
  3. alexlee.com at 1.1 s1.1 s
  4. alexlee.com at 1.5 s1.5 s
  5. alexlee.com at 1.9 s1.9 s
  6. alexlee.com at 2.3 s2.3 s
  7. alexlee.com at 2.6 s2.6 s
  8. alexlee.com at 3.0 s3.0 s

Speed

5 to fix62
  • Render-blocking requests

    4.3 s

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

  • Improve image delivery

    4.0 MB

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

  • Mobile performance score: 62

    62/100

    Your mobile performance score is 62 (desktop: 91). Pages that score under 90 lose visitors before the first paint.

  • Reduce unused JavaScript

    320 ms · 84 KiB

    About 84 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 320 ms faster on a phone.

  • FontAwesome CDN adds 122 ms

    122 ms

    FontAwesome CDN costs a phone 122 ms of main-thread work and 490 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.

  • 5 third-party services on the page

    5 third-party services load with your homepage (FontAwesome CDN, jQuery CDN and Google Fonts and others), adding 613 KiB and 159 ms of main-thread time.

  • 2 long tasks on the main thread

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

  • Minify JavaScript

    160 ms · 35 KiB

    35 KiB could be saved by minifying JavaScript.

  • Font display

    50 ms

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

  • Reduce unused CSS

    21 KiB

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

  • Phones get a much slower page than desktops

    Desktop scores 91 but mobile only 62. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

2 checks passed
  • Main-thread work: 0.8 s

    A phone's processor spends 0.8 s on main-thread work while loading, 150 ms of it running JavaScript. That is comfortably low.

  • Server response: 3 ms

    3 ms

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

Core Web Vitals

4 to fix100
  • Largest Contentful Paint: 7.6 s

    7.6 s

    Your largest element takes 7.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “CUSTOMERS ARE THE FOCUS OF EVERYTHING WE DO. We support gro…”.

  • First Contentful Paint: 5.3 s

    5.3 s

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

  • Time to Interactive: 7.6 s

    7.6 s

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

  • Speed Index: 5.3 s

    5.3 s

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

  • Tap response (INP) got 13% slower for real visitors

    +13%

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

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

    +16%

    Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' largest content (lcp) went from 1.8 s to 2.1 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: 2.2 s

    2.2 s

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

  • Real-user INP: 69 ms

    69 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.7 s

    1.7 s

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

  • Real-user TTFB: 772 ms

    772 ms

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

  • Cumulative Layout Shift: 0.003

    0.003

    The layout barely moves while loading (CLS 0.003, good is under 0.1).

  • Total Blocking Time: 46 ms

    46 ms

    Scripts block the page for only 46 ms while loading. Good is under 200 ms.

Images and page weight

1 to fix70
  • Page weight: 7.3 MB in 18 requests

    7.3 MB

    Your homepage downloads 7.3 MB in 18 requests on a phone: images 6.6 MB (6), scripts 634 KiB (3) and fonts 68 KiB (3). Under 2 MB keeps phones on slow connections fast.

  • About 2.1 g of CO₂ per visit

    2.08 g

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

8 to fixGoogle 7687
  • 2 text elements with low contrast

    2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

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

    All page content should be contained by landmarks: 2 elements on the page fail 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.

  • Zoom is disabled

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

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

  • 3 links without text

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

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

1 checks passed
  • 30 automated accessibility rules passed

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

SEO

9 to fixGoogle 6457
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No H1 headline

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

  • Title is short (4 characters)

    Your title is only 4 characters: “Home”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

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

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No robots.txt

    There is no robots.txt at alexlee.com/robots.txt, the first file search crawlers ask for.

  • 3 links crawlers can't follow

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

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

  • 19 internal links, 2 external

    The homepage links to 19 pages on alexlee.com and 2 external pages.

1 checks passed
  • XML sitemap found

    Your XML sitemap is reachable at https://www.alexlee.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.alexlee.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

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

  • Text is in the HTML

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

Other pages

2 to fix88
  • 2 pages share a title

    https://www.alexlee.com/en/about/history and https://www.alexlee.com/about/history all use the title “History”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 13 pages without a meta description

    https://www.alexlee.com/about, https://www.alexlee.com/en/about/community, https://www.alexlee.com/en/about/history, https://www.alexlee.com/en/about/sustainability, https://www.alexlee.com/careers and https://www.alexlee.com/en/careers/why-alex-lee and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages with very little text

    https://www.alexlee.com/en/media/alex-lee-ink, https://www.alexlee.com/en/media/videos and https://www.alexlee.com/contact 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.

  • 13 internal pages checked

    We fetched 13 pages linked from your homepage and read each the way a search engine does.

5 checks passed
  • Linked pages load

    All 13 pages we checked loaded without an error.

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

Best practices

1 to fixGoogle 10093
  • 1 small tap target

    1 of 5 tappable elements near the top of the page is smaller than 24 px, hard to hit with a thumb.

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

3 to fix60
  • No social proof

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

  • 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 form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

    The homepage carries about 266 words of visible text.

2 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “CONTACT”.

  • 2 calls to action

    The homepage has 2 calls to action, for example “Contact” and “Learn More”.

Privacy and tracking

  • 7 cookies set on arrival

    7

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

  • 7 other companies contacted

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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

Upkeep, stack and company

  • The footer still says © 2021.

Stack

Framework
jQuery
Hosting
Azure

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 34 issues on alexlee.com, including 9 speed issues, 9 SEO issues 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