Website review, no card needed

intact-tech.com logo

intact-tech.com website review

Visit site (opens in a new tab)Reviewed 28 October 202626 issues · 72 checks

This review found 26 issues worth fixing on intact-tech.com, 13 of them high impact, across 72 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

Full-page screenshot of intact-tech.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. intact-tech.com at 0.4 s0.4 s
  2. intact-tech.com at 0.8 s0.8 s
  3. intact-tech.com at 1.3 s1.3 s
  4. intact-tech.com at 1.7 s1.7 s
  5. intact-tech.com at 2.1 s2.1 s
  6. intact-tech.com at 2.5 s2.5 s
  7. intact-tech.com at 3.0 s3.0 s
  8. intact-tech.com at 3.4 s3.4 s

Speed

7 to fix44
  • Improve image delivery

    11.9 s · 2.3 MB

    12 images could be 2.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 11.9 s faster on a phone.

  • Reduce unused JavaScript

    5.1 s · 548 KiB

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

  • Render-blocking requests

    1.6 s

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

  • Mobile performance score: 44

    44/100

    Your mobile performance score is 44 (desktop: 45). 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 CDN, Google Tag Manager and ShareThis and others), adding 1.1 MB and 509 ms of main-thread time.

  • Use efficient cache lifetimes

    300 ms · 55 KiB

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

  • Google CDN adds 267 ms

    267 ms

    Google CDN costs a phone 267 ms of main-thread work and 734 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.

  • Reduce unused CSS

    150 ms · 51 KiB

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

  • Legacy JavaScript

    150 ms · 15 KiB

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

  • Minify JavaScript

    150 ms · 15 KiB

    15 KiB could be saved by minifying JavaScript.

  • 5 long tasks on the main thread

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

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

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

2 checks passed
  • Main-thread work: 1.2 s

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

  • Server response: 2 ms

    2 ms

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

Core Web Vitals

4 to fix33
  • Largest Contentful Paint: 24.0 s

    24.0 s

    Your largest element takes 24.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

  • Time to Interactive: 24.0 s

    24.0 s

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

  • Cumulative Layout Shift: 0.991

    0.991

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

  • First Contentful Paint: 2.7 s

    2.7 s

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

2 checks passed
  • Speed Index: 3.2 s

    3.2 s

    Visually, the page fills in at 3.2 s (Speed Index), inside the 3.4 s “good” threshold.

  • Total Blocking Time: 126 ms

    126 ms

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

Images and page weight

2 to fix60
  • Page weight: 16.0 MB in 74 requests

    16.0 MB

    Your homepage downloads 16.0 MB in 74 requests on a phone: media 11.7 MB (3), images 2.6 MB (21) and scripts 1.0 MB (14). Under 2 MB keeps phones on slow connections fast.

  • 2 images far larger than shown

    112 KiB

    2 images are downloaded at several times the size a phone draws them, for example US-Federal-Government-768x768.png at 390 px wide, shown at 72 px. Resized copies would save about 112 KiB.

  • 4 images in older formats

    4 images (235 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.

  • About 4.5 g of CO₂ per visit

    4.53 g

    By the Sustainable Web Design model, a visit to your homepage emits about 4.53 g of CO₂e: 543.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 load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

4 to fixGoogle 8894
  • Certain ARIA roles must be contained by particular parents (3 elements)

    Certain ARIA roles must be contained by particular parents: 3 elements on the page fail this check, rated critical by axe-core.

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

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 26 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

3 to fixGoogle 9277
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No H1 headline

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

  • No social preview image

    No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 44 internal links, 3 external

    The homepage links to 44 pages on intact-tech.com and 3 external pages.

5 checks passed
  • Title: 50 characters

    Your title is a healthy 50 characters: “A different kind of ServiceNow consultant - Intact”.

  • Canonical URL set

    The canonical URL is https://intact-tech.com/.

  • Structured data in place

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

  • 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://intact-tech.com/sitemap_index.xml.

AI search readiness

100
  • No llms.txt

    There is no https://intact-tech.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 (559 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 13 pages without a meta description

    https://intact-tech.com/services, https://intact-tech.com/services/platform-strategy-governance, https://intact-tech.com/services/implementation, https://intact-tech.com/services/management-enhancement, https://intact-tech.com/about and https://intact-tech.com/about/our-people and 7 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://intact-tech.com/about/social-impact, whose canonical is https://intact-tech.com/about/commitments. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 14 internal pages checked

    We fetched 14 pages linked from your homepage and read each the way a search engine does.

5 checks passed
  • Linked pages load

    All 14 pages we checked loaded without an error.

  • 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 14 pages that loaded have a <title>.

Best practices

3 to fixGoogle 7385
  • 4 small tap targets

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

  • 3 third-party cookies

    3 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 4 JavaScript errors while loading

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

  • Browser-reported issues

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

100
  • No form on the homepage

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

  • About 624 words of copy

    The homepage carries about 624 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: “Book a Discovery Call”.

  • 5 calls to action

    The homepage has 5 calls to action, for example “Contact”, “Book a Discovery Call” and “Subscribe on LinkedIn”.

  • Social proof on the page

    Social proof on the homepage: 4 customer or partner logos, a star rating and 6 trust badges.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 1 email 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

1 to fix
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads 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.

  • 4 cookies set on arrival

    4

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

  • 15 other companies contacted

    Loading the homepage contacts 15 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 intact-tech.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
Tailwind CSS
Analytics
Google Analytics

Company

Employees
235

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 intact-tech.com, including 11 speed issues and 3 SEO issues. 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