Website review, no card needed

westcontrol.com logo

westcontrol.com website review

Visit site (opens in a new tab)Reviewed 23 October 202629 issues · 75 checks

This review found 29 issues worth fixing on westcontrol.com, 9 of them high impact, across 75 checks. The most urgent: use efficient cache lifetimes. 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.1 s1.1 sMay 2Oct 171.7 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.0 s
May 9, 20261.9 s
May 16, 20261.9 s
May 23, 20261.9 s
May 30, 20261.8 s
Jun 6, 20261.6 s
Jun 13, 20261.3 s
Jun 20, 20261.3 s
Jun 27, 20261.2 s
Jul 4, 20261.4 s
Jul 11, 20261.6 s
Jul 18, 20261.8 s
Jul 25, 20262.0 s
Aug 1, 20261.6 s
Aug 8, 20261.6 s
Aug 15, 20261.5 s
Aug 22, 20261.7 s
Aug 29, 20261.8 s
Sep 5, 20261.9 s
Sep 12, 20262.0 s
Sep 19, 20261.9 s
Sep 26, 20261.9 s
Oct 3, 20261.9 s
Oct 10, 20261.8 s
Oct 17, 20261.7 s
Real-visitor tap response (INP)75th percentile, phones
90 ms70 msJun 13Oct 379 ms
Show as table
DateReal-visitor tap response (INP)
Jun 13, 202672 ms
Jun 20, 202672 ms
Jun 27, 202672 ms
Jul 4, 202675 ms
Jul 11, 202678 ms
Aug 1, 202680 ms
Aug 8, 202682 ms
Aug 15, 202684 ms
Aug 22, 202687 ms
Aug 29, 202687 ms
Sep 5, 202688 ms
Sep 12, 202687 ms
Sep 19, 202686 ms
Sep 26, 202687 ms
Oct 3, 202679 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 westcontrol.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. westcontrol.com at 0.4 s0.4 s
  2. westcontrol.com at 0.9 s0.9 s
  3. westcontrol.com at 1.3 s1.3 s
  4. westcontrol.com at 1.7 s1.7 s
  5. westcontrol.com at 2.1 s2.1 s
  6. westcontrol.com at 2.6 s2.6 s
  7. westcontrol.com at 3.0 s3.0 s
  8. westcontrol.com at 3.4 s3.4 s

Speed

7 to fix58
  • Use efficient cache lifetimes

    4.8 s · 2.4 MB

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

  • Reduce unused JavaScript

    1.4 s · 1.2 MB

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

  • Render-blocking requests

    2.3 s

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

  • Improve image delivery

    850 ms · 763 KiB

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

  • Mobile performance score: 58

    58/100

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (lordicon.com, Google Tag Manager and Facebook and others), adding 718 KiB and 638 ms of main-thread time.

  • Google Tag Manager adds 201 ms

    201 ms

    Google Tag Manager costs a phone 201 ms of main-thread work and 301 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 long tasks on the main thread

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

  • Legacy JavaScript

    29 KiB

    Polyfills for old browsers add 29 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.

2 checks passed
  • Main-thread work: 1.8 s

    A phone's processor spends 1.8 s on main-thread work while loading, 827 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

7 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: 9.8 s

    9.8 s

    Your largest element takes 9.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Precision and quality to world class products Your turnkey …”.

  • Time to Interactive: 9.8 s

    9.8 s

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

  • Speed Index: 6.1 s

    6.1 s

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

  • Real-user TTFB: 1.5 s

    1.5 s

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

  • Cumulative Layout Shift: 0.167

    0.167

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

  • First Contentful Paint: 2.0 s

    2.0 s

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

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

    +15%

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

5 checks passed
  • Real-user LCP: 1.7 s

    1.7 s

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

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

    1.5 s

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

  • Largest content (LCP) got 11% faster for real visitors

    -11%

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

  • Total Blocking Time: 195 ms

    195 ms

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

Images and page weight

2 to fix75
  • Page weight: 2.9 MB in 79 requests

    2.9 MB

    Your homepage downloads 2.9 MB in 79 requests on a phone: images 1.8 MB (15), scripts 868 KiB (22) and fonts 129 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • 7 images in older formats

    7 images (602 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

  • 1 image below the first screen load straight away

    1 image further down the page (31 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 0.8 g of CO₂ per visit

    0.82 g

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

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

3 to fixGoogle 9296
  • 4 text elements with low contrast

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

  • 10 links without text

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

  • ARIA role should be appropriate for the element (3 elements)

    ARIA role should be appropriate for the element: 3 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (3 elements).

2 checks passed
  • Every image has alt text

    All 19 images in the HTML carry an alt attribute.

  • 49 automated accessibility rules passed

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

SEO

2 to fixGoogle 10089
  • Title is short (18 characters)

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

  • No robots.txt

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

  • 51 internal links, 1 external

    The homepage links to 51 pages on westcontrol.com and 1 external page.

6 checks passed
  • Meta description: 123 characters

    Your meta description is 123 characters: “Westcontrol is your turnkey electronic manufacturing supplier; a team dedicated to turning ideas into innovative soluti…”.

  • One H1 headline

    Your main headline reads: “Precision and quality to world class products”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, WebPage and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • XML sitemap found

    Your XML sitemap is reachable at https://westcontrol.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://westcontrol.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 (372 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix70
  • 1 page without a title

    https://westcontrol.com/wp-content/uploads/2026/04/Sertifikat-14001-Westcontrol-Berget-2025.pdf%20 has no <title>, so Google invents the link text in results.

  • 8 pages without a meta description

    https://westcontrol.com/services/development, https://westcontrol.com/services/prototypes-and-industrialization, https://westcontrol.com/services/electronic-manufacturing, https://westcontrol.com/services/machining, https://westcontrol.com/services/cable and https://westcontrol.com/services/logistics and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://westcontrol.com/Compliance, whose canonical is https://westcontrol.com/compliance. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page without an H1

    https://westcontrol.com/wp-content/uploads/2026/04/Sertifikat-14001-Westcontrol-Berget-2025.pdf%20 has no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page slow to respond

    https://westcontrol.com/services/electronic-manufacturing took over 3 s to send its HTML from our server.

  • 15 internal pages checked

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

3 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

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

Best practices

1 to fixGoogle 9693
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Uncaught Error: Looks like your website URL has changed. To ensure the proper functioning of your banner, update the re…”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • Thin social proof

    Social proof on the homepage: 4 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

  • Only about 189 words

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

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “GET IN TOUCH”.

  • 3 calls to action

    The homepage has 3 calls to action, for example “Contact” and “GET IN TOUCH”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 4 trackers load before any consent

    4

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

  • 3 cookies set on arrival

    3

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

  • 8 other companies contacted

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

1 checks passed
  • Consent tool: CookieYes

    A consent management tool (CookieYes) 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 westcontrol.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 29 issues on westcontrol.com, including 14 speed issues, 2 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