creationtech.com website review

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

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

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

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

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Hubspot and LinkedIn Ads and others), adding 649 KiB and 462 ms of main-thread time.

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

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

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

18 KiB could be saved by minifying JavaScript.

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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

4 KiB could be saved by minifying CSS.

Your largest element takes 18.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Reduce Manufacturing Risk and Scale with Confidence Creatio…”.

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

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

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

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

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

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

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

Your homepage downloads 2.7 MB in 160 requests on a phone: scripts 959 KiB (57), images 926 KiB (37) and fonts 575 KiB (10). Under 2 MB keeps phones on slow connections fast.

2 images (532 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 is downloaded at several times the size a phone draws it, for example ct-locations-map.svg at 1,292 px wide, shown at 390 px. Resized copies would save about 17 KiB.

3 images further down the page (163 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.

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

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

The homepage links to 132 pages on creationtech.com and 5 external pages.

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

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

2 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'animate')”.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

creationtech.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

creationtech.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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.

Your longest form asks for 11 fields (9 required). Every extra field lowers completion.

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

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

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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

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

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