Website review, no card needed

nwconstruction.com logo

nwconstruction.com website review

Visit site (opens in a new tab)Reviewed 19 November 202626 issues · 77 checks

This review found 26 issues worth fixing on nwconstruction.com, 7 of them high impact, across 77 checks. The most urgent: improve image delivery. 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.4 s1.3 sMay 30Nov 141.4 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.3 s
Jun 6, 20261.3 s
Jun 13, 20261.3 s
Jun 20, 20261.4 s
Jun 27, 20261.4 s
Jul 4, 20261.4 s
Jul 11, 20261.4 s
Jul 18, 20261.3 s
Jul 25, 20261.3 s
Aug 1, 20261.4 s
Aug 8, 20261.4 s
Aug 15, 20261.4 s
Aug 22, 20261.3 s
Aug 29, 20261.3 s
Sep 5, 20261.3 s
Sep 12, 20261.4 s
Sep 19, 20261.3 s
Sep 26, 20261.3 s
Oct 3, 20261.3 s
Oct 10, 20261.4 s
Oct 17, 20261.4 s
Oct 24, 20261.4 s
Oct 31, 20261.4 s
Nov 7, 20261.4 s
Nov 14, 20261.4 s
Real-visitor tap response (INP)75th percentile, phones
95 ms85 msMay 30Nov 1489 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 202694 ms
Jun 6, 202689 ms
Jun 13, 202686 ms
Jun 20, 202686 ms
Jun 27, 202688 ms
Jul 4, 202689 ms
Jul 11, 202693 ms
Jul 18, 202692 ms
Jul 25, 202690 ms
Aug 1, 202694 ms
Aug 8, 202691 ms
Aug 15, 202691 ms
Aug 22, 202694 ms
Aug 29, 202691 ms
Sep 5, 202689 ms
Sep 12, 202693 ms
Sep 19, 202689 ms
Sep 26, 202689 ms
Oct 3, 202693 ms
Oct 10, 202689 ms
Oct 17, 202689 ms
Oct 24, 202691 ms
Oct 31, 202687 ms
Nov 7, 202691 ms
Nov 14, 202689 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 nwconstruction.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. nwconstruction.com at 0.5 s0.5 s
  2. nwconstruction.com at 0.9 s0.9 s
  3. nwconstruction.com at 1.4 s1.4 s
  4. nwconstruction.com at 1.8 s1.8 s
  5. nwconstruction.com at 2.3 s2.3 s
  6. nwconstruction.com at 2.8 s2.8 s
  7. nwconstruction.com at 3.2 s3.2 s
  8. nwconstruction.com at 3.7 s3.7 s

Speed

3 to fix67
  • Improve image delivery

    1.5 s · 277 KiB

    4 images could be 277 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.5 s faster on a phone.

  • Mobile performance score: 67

    67/100

    Your mobile performance score is 67. Pages that score under 90 lose visitors before the first paint.

  • Reduce unused JavaScript

    600 ms · 201 KiB

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

  • 4 third-party services on the page

    4 third-party services load with your homepage (Google Tag Manager, Cloudflare and Google Fonts and others), adding 344 KiB and 153 ms of main-thread time.

  • Legacy JavaScript

    150 ms · 10 KiB

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

  • Use efficient cache lifetimes

    150 ms · 4 KiB

    1 file is served with short cache lifetimes, so returning visitors download them again (4 KiB).

  • Render-blocking requests

    150 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 150 ms.

  • 3 long tasks on the main thread

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

  • Reduce unused CSS

    10 KiB

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

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

  • Minify CSS

    4 KiB

    4 KiB could be saved by minifying CSS.

2 checks passed
  • Main-thread work: 0.5 s

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

  • Server response: 1 ms

    1 ms

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

Core Web Vitals

6 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: 11.1 s

    11.1 s

    Your largest element takes 11.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We build your amazing future We provide services in the ent…”.

  • Time to Interactive: 11.1 s

    11.1 s

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

  • Speed Index: 8.0 s

    8.0 s

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

  • Real-user TTFB: 831 ms

    831 ms

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

  • 3 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -2%

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

  • Largest content (LCP) held steady for real visitors

    +7%

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

7 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: 79 ms

    79 ms

    Real visitors wait 79 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.2 s

    1.2 s

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

  • Total Blocking Time: 65 ms

    65 ms

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

  • Cumulative Layout Shift: 0

    0

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

  • First Contentful Paint: 0.9 s

    0.9 s

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

Images and page weight

1 to fix85
  • Page weight: 2.7 MB in 29 requests

    2.7 MB

    Your homepage downloads 2.7 MB in 29 requests on a phone: images 2.0 MB (17), scripts 703 KiB (4) and fonts 42 KiB (3). Under 2 MB keeps phones on slow connections fast.

  • About 0.8 g of CO₂ per visit

    0.77 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.77 g of CO₂e: 92.4 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 9397
  • All page content should be contained by landmarks (7 elements)

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

  • Zoom is disabled

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

2 checks passed
  • Every image has alt text

    All 6 images in the HTML carry an alt attribute.

  • 30 automated accessibility rules passed

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

SEO

6 to fixGoogle 10066
  • No H1 headline

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

  • Title is short (10 characters)

    Your title is only 10 characters: “North West”. 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.

  • Meta description is long (200 characters)

    Your meta description is 200 characters; Google truncates after about 160, so the end of your pitch is cut.

  • No XML sitemap

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

  • No X (Twitter) card tag

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

  • 67 internal links, 3 external

    The homepage links to 67 pages on nwconstruction.com and 3 external pages.

2 checks passed
  • 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.nwconstruction.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 (227 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix83
  • 16 pages share a title

    /, https://www.nwconstruction.com/az, https://www.nwconstruction.com/ru, https://www.nwconstruction.com/en/projects/completed-projects, https://www.nwconstruction.com/en/about/who-we-are and https://www.nwconstruction.com/en/about and 10 others all use the title “North West”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages without a meta description

    https://www.nwconstruction.com/en/about/clients-and-partners and https://www.nwconstruction.com/en/about/clients-and-partners/clients have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 pages without an H1

    https://www.nwconstruction.com/az, https://www.nwconstruction.com/ru, https://www.nwconstruction.com/en/projects/completed-projects, https://www.nwconstruction.com/en/about/who-we-are, https://www.nwconstruction.com/en/about and https://www.nwconstruction.com/en/about/vision-mission-values-1 and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages with very little text

    https://www.nwconstruction.com/ru and https://www.nwconstruction.com/en/about/clients-and-partners/clients 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.

  • 5 pages slow to respond

    https://www.nwconstruction.com/en/projects/completed-projects, https://www.nwconstruction.com/en/about/who-we-are, https://www.nwconstruction.com/en/about, https://www.nwconstruction.com/en/about/vision-mission-values-1 and https://www.nwconstruction.com/en/about/corporate-structure took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

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

  • 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

Google 100100
  • Missing source maps

    Large scripts ship without source maps.

3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix67
  • 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 direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • Only about 173 words

    The homepage has only about 173 words of visible text; thin pages give Google and first-time buyers little to go on.

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

3 checks passed
  • Clear next step on the first screen

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

  • 2 calls to action

    The homepage has 2 calls to action, for example “Contact us”.

  • Analytics in place

    Analytics detected: Google Analytics and Cloudflare Web Analytics.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 3 cookies set on arrival

    3

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

  • 5 other companies contacted

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

Upkeep, stack and company

Stack

Analytics
Google Analytics
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 26 issues on nwconstruction.com, including 9 speed issues, 6 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