Website review, no card needed

sitepro.com logo

sitepro.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 sitepro.com, 12 of them high impact, across 82 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

Real-visitor load time (LCP)75th percentile, phones
4.4 s2.2 sMay 2Oct 174.0 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20263.0 s
May 9, 20262.9 s
May 16, 20262.9 s
May 23, 20262.6 s
May 30, 20262.5 s
Jun 6, 20262.4 s
Jun 13, 20262.5 s
Jun 20, 20262.7 s
Jun 27, 20262.7 s
Jul 4, 20262.7 s
Jul 11, 20262.9 s
Jul 18, 20262.7 s
Jul 25, 20262.9 s
Aug 1, 20263.0 s
Aug 8, 20262.9 s
Aug 15, 20263.1 s
Aug 22, 20263.3 s
Aug 29, 20263.2 s
Sep 5, 20263.2 s
Sep 12, 20263.5 s
Sep 19, 20263.8 s
Sep 26, 20264.1 s
Oct 3, 20264.1 s
Oct 10, 20264.0 s
Oct 17, 20264.0 s
Real-visitor tap response (INP)75th percentile, phones
199 ms184 msSep 19Oct 17188 ms
Show as table
DateReal-visitor tap response (INP)
Sep 19, 2026192 ms
Sep 26, 2026197 ms
Oct 3, 2026197 ms
Oct 10, 2026186 ms
Oct 17, 2026188 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 sitepro.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. sitepro.com at 0.6 s0.6 s
  2. sitepro.com at 1.1 s1.1 s
  3. sitepro.com at 1.7 s1.7 s
  4. sitepro.com at 2.2 s2.2 s
  5. sitepro.com at 2.8 s2.8 s
  6. sitepro.com at 3.3 s3.3 s
  7. sitepro.com at 3.9 s3.9 s
  8. sitepro.com at 4.4 s4.4 s

Speed

9 to fix47
  • Reduce unused JavaScript

    4.1 s · 687 KiB

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

  • Use efficient cache lifetimes

    3.7 s · 695 KiB

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

  • Render-blocking requests

    1.1 s

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

  • Mobile performance score: 47

    47/100

    Your mobile performance score is 47 (desktop: 61). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Improve image delivery

    900 ms · 618 KiB

    4 images could be 618 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 900 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.6 MB and 955 ms of main-thread time.

  • Google Tag Manager adds 452 ms

    452 ms

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

  • Main-thread work: 3.1 s

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

  • 1,579 HTML elements

    The page has 1,579 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • 13 long tasks on the main thread

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

  • Legacy JavaScript

    42 KiB

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

  • Reduce unused CSS

    25 KiB

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

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

  • Duplicated JavaScript

    1 KiB

    1 KiB JavaScript is shipped twice across bundles.

1 checks passed
  • Server response: 9 ms

    9 ms

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

Core Web Vitals

10 to fix67
  • 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 LCP: 4.0 s

    4.0 s

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

  • First Contentful Paint: 8.2 s

    8.2 s

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

  • Largest Contentful Paint: 20.7 s

    20.7 s

    Your largest element takes 20.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “SitePro is a unified platform that empowers operators with …”.

  • Time to Interactive: 20.8 s

    20.8 s

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

  • Speed Index: 8.7 s

    8.7 s

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

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

    +35%

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

  • Real-user FCP: 2.9 s

    2.9 s

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

  • Real-user TTFB: 1.6 s

    1.6 s

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

  • Total Blocking Time: 400 ms

    400 ms

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

  • 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 192 ms to 188 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

3 checks passed
  • Real-user INP: 188 ms

    188 ms

    Real visitors wait 188 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

3 to fix53
  • Page weight: 4.5 MB in 115 requests

    4.5 MB

    Your homepage downloads 4.5 MB in 115 requests on a phone: images 2.0 MB (20), scripts 1.8 MB (49) and media 524 KiB (1). Under 2 MB keeps phones on slow connections fast.

  • 3 images far larger than shown

    346 KiB

    3 images are downloaded at several times the size a phone draws them, for example Nutrien-Grey-1.svg at 800 px wide, shown at 54 px. Resized copies would save about 346 KiB.

  • 1 image below the first screen load straight away

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

  • About 1.3 g of CO₂ per visit

    1.28 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

2 to fixGoogle 9797
  • Interactive controls must not be nested (4 elements)

    Interactive controls must not be nested: 4 elements on the page fail this check, rated serious by axe-core.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

2 checks passed
  • Every image has alt text

    All 59 images in the HTML carry an alt attribute.

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

SEO

3 to fixGoogle 8591
  • Meta description is long (167 characters)

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

  • 4 links with vague text

    4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • 143 internal links, 12 external

    The homepage links to 143 pages on sitepro.com and 12 external pages.

7 checks passed
  • One H1 headline

    Your main headline reads: “Stop Working in the Dark”.

  • Title: 62 characters

    Your title is a healthy 62 characters: “SitePro - Industrial Automation Software for Real-Time Control”.

  • Canonical URL set

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

  • Structured data in place

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

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing url, description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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.

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://www.sitepro.com/llms.txt (35 KiB, 150 links, though it should open with a “# Title” line), a plain-text guide to the site for AI tools.

Other pages

100
  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 65 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

3 to fixGoogle 9285
  • 33 small tap targets

    33 of 80 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix79
  • 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 phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • 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 opening hours

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

  • No form on the homepage

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

  • No map or directions link

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

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

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

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Careers Join our team” and “Contact Us We’re here to help”.

  • 19 calls to action

    The homepage has 19 calls to action, for example “Get Started”, “Plans & Pricing” and “Schedule a Demo”.

  • Social proof on the page

    Social proof on the homepage: 14 testimonial or review blocks, 4 customer or partner logos and 3 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager and PostHog.

Privacy and tracking

  • 6 trackers load before any consent

    6

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

  • 10 cookies set on arrival

    10

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

  • 25 other companies contacted

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

1 checks passed
  • Consent tool: Termly

    A consent management tool (Termly) 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 sitepro.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 | PostHog

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 sitepro.com, including 19 speed issues, 3 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