Website review, no card needed

alphaefficiency.com logo

alphaefficiency.com website review

Visit site (opens in a new tab)Reviewed 17 November 202623 issues · 80 checks

This review found 23 issues worth fixing on alphaefficiency.com, 6 of them high impact, across 80 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
3.4 s1.9 sMay 30Nov 142.6 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.5 s
Jun 6, 20262.5 s
Jun 13, 20262.5 s
Jun 20, 20262.5 s
Jun 27, 20262.7 s
Jul 4, 20262.8 s
Jul 11, 20263.1 s
Jul 18, 20263.1 s
Jul 25, 20263.3 s
Aug 1, 20263.1 s
Aug 8, 20262.8 s
Aug 15, 20262.9 s
Aug 22, 20262.9 s
Aug 29, 20263.1 s
Sep 5, 20263.1 s
Sep 12, 20262.8 s
Sep 19, 20262.4 s
Oct 24, 20262.1 s
Oct 31, 20262.2 s
Nov 7, 20262.5 s
Nov 14, 20262.6 s
Real-visitor tap response (INP)75th percentile, phones
512 ms173 msMay 30Nov 14254 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026380 ms
Jun 6, 2026381 ms
Jun 13, 2026444 ms
Jun 20, 2026450 ms
Jun 27, 2026424 ms
Jul 4, 2026473 ms
Oct 24, 2026212 ms
Oct 31, 2026248 ms
Nov 7, 2026248 ms
Nov 14, 2026254 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 alphaefficiency.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

6 to fix93
  • Render-blocking requests

    1.2 s

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

  • Reduce unused CSS

    700 ms · 120 KiB

    About 120 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 700 ms faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and posthog.com and others), adding 1.1 MB and 636 ms of main-thread time.

  • Use efficient cache lifetimes

    512 KiB

    19 files are served with short cache lifetimes, so returning visitors download them again (512 KiB).

  • Reduce unused JavaScript

    388 KiB

    About 388 KiB of JavaScript is downloaded but never used on this page.

  • Google Tag Manager adds 303 ms

    303 ms

    Google Tag Manager costs a phone 303 ms of main-thread work and 515 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.

  • Improve image delivery

    151 KiB

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

  • 7 long tasks on the main thread

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

  • Legacy JavaScript

    44 KiB

    Polyfills for old browsers add 44 KiB JavaScript that modern phones do not need.

  • Duplicated JavaScript

    16 KiB

    16 KiB JavaScript is shipped twice across bundles.

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

3 checks passed
  • Mobile performance score: 93

    93/100

    Your mobile performance score is 93. That is in Google's “good” band (90 and up).

  • Main-thread work: 1.3 s

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

  • Server response: 4 ms

    4 ms

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

Core Web Vitals

10 to fix0
  • 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: 0.36

    0.36

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

  • Time to Interactive: 14.1 s

    14.1 s

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

  • Real-user LCP: 2.6 s

    2.6 s

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

  • Real-user INP: 262 ms

    262 ms

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

  • Real-user FCP: 1.9 s

    1.9 s

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

  • Real-user TTFB: 1.2 s

    1.2 s

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

  • First Contentful Paint: 2.1 s

    2.1 s

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

  • Largest Contentful Paint: 2.6 s

    2.6 s

    Your largest element takes 2.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Right statue”.

  • 9 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    +2%

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

4 checks passed
  • Tap response (INP) got 34% faster for real visitors

    -34%

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

  • Speed Index: 3.2 s

    3.2 s

    Visually, the page fills in at 3.2 s (Speed Index), inside the 3.4 s “good” threshold.

  • Total Blocking Time: 155 ms

    155 ms

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

  • Cumulative Layout Shift: 0.011

    0.011

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

Images and page weight

1 to fix90
  • 1 image far larger than shown

    40 KiB

    1 image is downloaded at several times the size a phone draws it, for example brian2.webp at 1,466 px wide, shown at 421 px. Resized copies would save about 40 KiB.

  • About 0.5 g of CO₂ per visit

    0.52 g

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

3 checks passed
  • Page weight: 1.8 MB in 103 requests

    1.8 MB

    Your homepage downloads 1.8 MB in 103 requests on a phone: scripts 1.2 MB (26), images 393 KiB (43) and stylesheets 138 KiB (2). That is a lean page.

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

Accessibility

2 to fixGoogle 9697
  • 20 text elements with low contrast

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

  • 4 form fields without a label

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

2 checks passed
  • Every image has alt text

    All 73 images in the HTML carry an alt attribute.

  • 45 automated accessibility rules passed

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

SEO

Google 100100
  • 82 internal links, 9 external

    The homepage links to 82 pages on alphaefficiency.com and 9 external pages.

8 checks passed
  • Meta description: 136 characters

    Your meta description is 136 characters: “Custom websites engineered for speed, SEO, and conversions—built by our Chicago web design & development team. Request …”.

  • One H1 headline

    Your main headline reads: “Website Design, SEO & AI Development Agency.”.

  • Title: 60 characters

    Your title is a healthy 60 characters: “Chicago Web Design & AI Development - Conversion‑First Sites”.

  • Canonical URL set

    The canonical URL is https://alphaefficiency.com/.

  • Structured data in place

    Structured data found: 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://alphaefficiency.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

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

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

  • Organization data: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.

  • Text is in the HTML

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

Other pages

100
  • 1 page with very little text

    https://alphaefficiency.com/other-services 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.

  • 15 internal pages checked

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

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

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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

2 to fixGoogle 9687
  • 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.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • No call to action on the first screen

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

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • About 851 words of copy

    The homepage carries about 851 words of visible text.

7 checks passed
  • 10 calls to action

    The homepage has 10 calls to action, for example “Pricing”, “Contact” and “Schedule a Call”.

  • 1 short form

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

  • Social proof on the page

    Social proof on the homepage: 19 testimonial or review blocks, 33 customer or partner logos and “600+ Businesses”.

  • Analytics in place

    Analytics detected: Google Tag Manager, HubSpot and Cloudflare Web Analytics.

  • Direct contact links

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

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call 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

  • 7 trackers load before any consent

    7

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and LinkedIn Insight and 2 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.

  • 24 cookies set on arrival

    24

    Opening the homepage sets 24 cookies, 10 of them by other companies (measured from a US location before any click).

  • 36 other companies contacted

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

Upkeep, stack and company

Stack

CMS
WordPress
Framework
Astro
Analytics
Google Tag Manager
Hosting
Cloudflare

Hiring

Hiring
1 open role
Job board
careers page

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 23 issues on alphaefficiency.com, including 16 speed 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