Website review, no card needed

truepointscanning.com logo

truepointscanning.com website review

Visit site (opens in a new tab)Reviewed 2 November 202633 issues · 89 checks

This review found 33 issues worth fixing on truepointscanning.com, 11 of them high impact, across 89 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
3.4 s1.4 sMay 16Oct 311.7 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.8 s
May 23, 20262.8 s
May 30, 20262.8 s
Jun 6, 20263.0 s
Jun 13, 20263.1 s
Jun 20, 20263.1 s
Jun 27, 20263.1 s
Jul 4, 20263.0 s
Jul 11, 20263.0 s
Jul 18, 20263.0 s
Jul 25, 20262.9 s
Aug 1, 20262.7 s
Aug 8, 20262.5 s
Aug 15, 20262.3 s
Aug 22, 20262.0 s
Aug 29, 20261.9 s
Sep 5, 20261.8 s
Sep 12, 20261.7 s
Sep 19, 20261.6 s
Sep 26, 20261.6 s
Oct 3, 20261.6 s
Oct 10, 20261.7 s
Oct 17, 20261.7 s
Oct 24, 20261.7 s
Oct 31, 20261.7 s
Real-visitor tap response (INP)75th percentile, phones
152 ms91 msMay 16Oct 31138 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026130 ms
May 23, 2026128 ms
May 30, 2026129 ms
Jun 6, 2026139 ms
Jun 13, 2026142 ms
Jun 20, 2026143 ms
Jun 27, 2026145 ms
Jul 4, 2026141 ms
Jul 11, 2026137 ms
Jul 18, 2026136 ms
Jul 25, 2026134 ms
Aug 1, 2026126 ms
Aug 8, 2026123 ms
Aug 15, 2026117 ms
Aug 22, 2026106 ms
Aug 29, 2026105 ms
Sep 5, 202698 ms
Sep 12, 202698 ms
Sep 19, 2026101 ms
Sep 26, 2026106 ms
Oct 3, 2026119 ms
Oct 10, 2026127 ms
Oct 17, 2026134 ms
Oct 24, 2026136 ms
Oct 31, 2026138 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 truepointscanning.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

11 to fix32
  • Reduce unused JavaScript

    2.9 s · 794 KiB

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

  • Use efficient cache lifetimes

    2.5 s · 811 KiB

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

  • Render-blocking requests

    1.4 s

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

  • Mobile performance score: 32

    32/100

    Your mobile performance score is 32. 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 (Google Tag Manager, Hotjar and website-files.com and others), adding 2.9 MB and 1.3 s of main-thread time.

  • Reduce unused CSS

    590 ms · 134 KiB

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

  • Main-thread work: 4.0 s

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

  • Google Tag Manager adds 317 ms

    317 ms

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

  • website-files.com adds 207 ms

    207 ms

    website-files.com costs a phone 207 ms of main-thread work and 1.2 MB 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.

  • Hotjar adds 278 ms

    278 ms

    Hotjar costs a phone 278 ms of main-thread work and 255 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 Maps adds 124 ms

    124 ms

    Google Maps costs a phone 124 ms of main-thread work and 393 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.

  • 20 long tasks on the main thread

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

  • Legacy JavaScript

    35 KiB

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

  • Improve image delivery

    19 KiB

    1 image could be 19 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

  • Minify CSS

    2 KiB

    2 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 3 ms

    3 ms

    Your server sent the HTML in 3 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.

  • Largest Contentful Paint: 14.1 s

    14.1 s

    Your largest element takes 14.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “3D LASER SCANNING SCAN TO CAD & SCAN TO BIM SERVICES Schedu…”.

  • Time to Interactive: 18.8 s

    18.8 s

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

  • Speed Index: 7.9 s

    7.9 s

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

  • Total Blocking Time: 904 ms

    904 ms

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

  • Cumulative Layout Shift: 0.272

    0.272

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

  • Real-user LCP: 2.5 s

    2.5 s

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

  • Real-user FCP: 2.2 s

    2.2 s

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

  • First Contentful Paint: 1.8 s

    1.8 s

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

  • 11 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +6%

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

4 checks passed
  • Real-user INP: 112 ms

    112 ms

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

  • Real-user CLS: 0.01

    0.01

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

  • Real-user TTFB: 637 ms

    637 ms

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

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

    -40%

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

Images and page weight

2 to fix81
  • Page weight: 3.4 MB in 130 requests

    3.4 MB

    Your homepage downloads 3.4 MB in 130 requests on a phone: scripts 2.1 MB (35), images 1.0 MB (51) and fonts 153 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    6a3ae605d06dc7535ecef9d7_GPRS 3D Laser Scanning Services 2-p is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • About 1.0 g of CO₂ per visit

    0.97 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

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

Accessibility

4 to fixGoogle 10096
  • All page content should be contained by landmarks (81 elements)

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

  • Document should not have more than one banner landmark (1 element)

    Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • 2 form fields without a label

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

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

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed
  • Every image has alt text

    All 101 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 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 3 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 9293
  • Meta description is long (287 characters)

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

  • 8 links with vague text

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

  • 163 internal links, 13 external

    The homepage links to 163 pages on truepointscanning.com and 13 external pages.

7 checks passed
  • One H1 headline

    Your main headline reads: “3D Laser Scanning”.

  • Title: 33 characters

    Your title is a healthy 33 characters: “3D Laser Scanning Services | GPRS”.

  • Canonical URL set

    The canonical URL is https://www.gp-radar.com/services/3d-laser-scanning.

  • Structured data in place

    Structured data found: Organization.

  • 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.gp-radar.com/sitemap.xml.

AI search readiness

100
4 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 description; contact details would complete it.

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://www.gp-radar.com/llms.txt (195 KiB, 1,495 links), 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 120 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 9278
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=25052822&Ver=2&mid=542ea6af-2cd5-4693-a15b-d0c86af230aa&bo=1&sid=f5cd7c00d68411f1ae862b5c7824d409&vid=f5cda150d68411f191790d2a42f17b76&vids=1&msclkid=N&pi=918639831&lg.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “User denied the request for Geolocation.”.

  • Requests the geolocation permission on page load

    Requests the geolocation permission on page load.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • Thin social proof

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

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

  • About 1,274 words of copy

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

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Request A Quote” and “Schedule Service”.

  • 22 calls to action

    The homepage has 22 calls to action, for example “contact”, “Request A Quote” and “Schedule”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • 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

  • 9 trackers load before any consent

    9

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

  • 21 cookies set on arrival

    21

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

  • 43 other companies contacted

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

1 checks passed
  • Consent tool: OneTrust

    A consent management tool (OneTrust) 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 truepointscanning.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
Webflow
Analytics
Google Tag Manager
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on truepointscanning.com, including 21 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