Programmable

Website review, no card needed

sterlingedmonton.com logo

sterlingedmonton.com website review

Visit site (opens in a new tab)Reviewed 21 October 202625 issues · 78 checks

This review found 25 issues worth fixing on sterlingedmonton.com, 12 of them high impact, across 78 checks. The most urgent: reduce unused JavaScript. 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

Site score

81B

Closest competitors among reviewed websites

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
1.5 s785 msMay 2Oct 171.3 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.0 s
May 9, 20261.0 s
May 16, 2026954 ms
May 23, 2026865 ms
May 30, 2026913 ms
Jun 6, 2026958 ms
Jun 13, 20261.0 s
Jun 20, 20261.1 s
Jun 27, 20261.1 s
Jul 4, 20261.2 s
Jul 11, 20261.2 s
Jul 18, 20261.1 s
Jul 25, 20261.1 s
Aug 1, 20261.1 s
Aug 8, 20261.0 s
Aug 15, 20261.1 s
Aug 22, 20261.2 s
Aug 29, 20261.2 s
Sep 5, 20261.3 s
Sep 12, 20261.3 s
Sep 19, 20261.4 s
Sep 26, 20261.4 s
Oct 3, 20261.4 s
Oct 10, 20261.4 s
Oct 17, 20261.3 s
Real-visitor tap response (INP)75th percentile, phones
114 ms101 msMay 2Oct 17112 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026109 ms
May 9, 2026104 ms
May 16, 2026104 ms
May 23, 2026105 ms
May 30, 2026111 ms
Jun 6, 2026112 ms
Jun 13, 2026112 ms
Jun 20, 2026112 ms
Jun 27, 2026109 ms
Jul 4, 2026111 ms
Jul 11, 2026105 ms
Jul 18, 2026103 ms
Jul 25, 2026104 ms
Aug 1, 2026104 ms
Aug 8, 2026104 ms
Aug 15, 2026104 ms
Aug 22, 2026103 ms
Aug 29, 2026102 ms
Sep 5, 2026104 ms
Sep 12, 2026104 ms
Sep 19, 2026106 ms
Sep 26, 2026105 ms
Oct 3, 2026104 ms
Oct 10, 2026110 ms
Oct 17, 2026112 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

www.sterlingedmonton.com (opens in a new tab)
Full-page screenshot of sterlingedmonton.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. sterlingedmonton.com at 2.4 s2.4 s
  2. sterlingedmonton.com at 4.8 s4.8 s
  3. sterlingedmonton.com at 7.2 s7.2 s
  4. sterlingedmonton.com at 9.6 s9.6 s
  5. sterlingedmonton.com at 12.0 s12.0 s
  6. sterlingedmonton.com at 14.4 s14.4 s
  7. sterlingedmonton.com at 16.8 s16.8 s
  8. sterlingedmonton.com at 19.1 s19.1 s

Speed

9 to fix34

  • Reduce unused JavaScript

    3.9 s · 958 KiB

    About 958 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.9 s faster on a phone.

  • Main-thread work: 35.3 s

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

  • Use efficient cache lifetimes

    1.2 s · 467 KiB

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

  • Mobile performance score: 34

    34/100

    Your mobile performance score is 34. 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 (reddit, Google Tag Manager and hsappstatic.net and others), adding 2.2 MB and 2.1 s of main-thread time.

  • reddit adds 738 ms

    738 ms

    reddit costs a phone 738 ms of main-thread work and 39 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.

  • Google Tag Manager adds 539 ms

    539 ms

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

  • hsappstatic.net adds 322 ms

    322 ms

    hsappstatic.net costs a phone 322 ms of main-thread work and 695 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.

  • Render-blocking requests

    350 ms

    5 files block the first paint until they finish downloading. Deferring or inlining them could save about 350 ms.

  • 20 long tasks on the main thread

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

  • Reduce unused CSS

    150 ms · 44 KiB

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

  • Improve image delivery

    150 ms · 29 KiB

    2 images could be 29 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

  • Legacy JavaScript

    150 ms · 24 KiB

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

  • 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: 36 ms

    36 ms

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

Core Web Vitals

8 to fix100

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

  • Largest Contentful Paint: 16.4 s

    16.4 s

    Your largest element takes 16.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “21A0078 79 80 81 82 83 84Average”.

  • Time to Interactive: 32.2 s

    32.2 s

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

  • First Contentful Paint: 4.9 s

    4.9 s

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

  • Speed Index: 8.4 s

    8.4 s

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

  • Total Blocking Time: 1.2 s

    1.2 s

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

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

    +31%

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

  • Real-user FCP: 2.6 s

    2.6 s

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

  • Tap response (INP) held steady for real visitors

    +4%

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

4 checks passed

  • Real-user LCP: 1.5 s

    1.5 s

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

  • Real-user INP: 127 ms

    127 ms

    Real visitors wait 127 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.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix85

  • Page weight: 2.9 MB in 137 requests

    2.9 MB

    Your homepage downloads 2.9 MB in 137 requests on a phone: scripts 2.4 MB (55), images 236 KiB (21) and stylesheets 117 KiB (12). Under 2 MB keeps phones on slow connections fast.

  • About 0.8 g of CO₂ per visit

    0.83 g

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

2 to fixGoogle 9697

  • 6 text elements with low contrast

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

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

2 checks passed

  • Every image has alt text

    All 16 images in the HTML carry an alt attribute.

  • 44 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: 44 passed and 2 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

Google 100100

  • 100 internal links, 5 external

    The homepage links to 100 pages on sterlingedmonton.com and 5 external pages.

8 checks passed

  • Meta description: 140 characters

    Your meta description is 140 characters: “Experience quality with Sterling Homes. Home builders in Edmonton dedicated to crafting your dream home with care. Star…”.

  • One H1 headline

    Your main headline reads: “Sterling Homes – We deliver Sterling homes”.

  • Title: 39 characters

    Your title is a healthy 39 characters: “Home Builders Edmonton - Sterling Homes”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, Organization, WebPage 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.sterlingedmonton.com/sitemap_index.xml.

AI search readiness

100

  • No llms.txt

    There is no https://www.sterlingedmonton.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: 4 of 6 facts

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

  • Text is in the HTML

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

Other pages

3 to fix88

  • 12 pages share a meta description

    https://www.sterlingedmonton.com/pre-sale-homes, https://www.sterlingedmonton.com/about-us/sterling-specifications, https://www.sterlingedmonton.com/communities, https://www.sterlingedmonton.com/get-started, https://www.sterlingedmonton.com/about-us and https://www.sterlingedmonton.com/about-us/meet-the-team and 6 others use the same meta description. A description written for each page earns more clicks.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.sterlingedmonton.com/resources/new-home-warranty-program-in-alberta, whose canonical is https://www.sterlingedmonton.com/resources/warranty-and-serviceq. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 2 pages without an H1

    https://www.sterlingedmonton.com/about-us and https://www.sterlingedmonton.com/resources/new-home-warranty-program-in-alberta have no <h1> headline, so visitors and search engines get no clear main topic.

  • 4 pages slow to respond

    https://www.sterlingedmonton.com/get-started, https://www.sterlingedmonton.com/about-us, https://www.sterlingedmonton.com/resources/new-home-warranty-program-in-alberta and https://www.sterlingedmonton.com/contact took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

5 checks passed

  • Linked pages load

    All 15 pages we checked loaded without an error.

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

  • 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

1 to fixGoogle 7797

  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • Browser-reported issues

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

3 checks passed

  • No console errors

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

  • Tap targets are thumb-sized

    9 of 10 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix80

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

  • 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 1,103 words of copy

    The homepage carries about 1,103 words of visible text.

4 checks passed

  • 5 calls to action

    The homepage has 5 calls to action, for example “Book an Appointment”, “Contact” and “Get Started”.

  • Social proof on the page

    Social proof on the homepage: 20 testimonial or review blocks and 1 customer or partner logo.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

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

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

  • 13 cookies set on arrival

    13

    Opening the homepage sets 13 cookies (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 sterlingedmonton.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
jQuery
Analytics
Google Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 25 issues on sterlingedmonton.com, including 17 speed issues and 1 conversion gap. 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