kicksaw.com website review

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

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

47 images could be 1.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.

8 third-party services load with your homepage (Drift, website-files.com and JSDelivr CDN and others), adding 4.5 MB and 503 ms of main-thread time.

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

Drift costs a phone 309 ms of main-thread work and 813 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.

About 174 KiB of JavaScript is downloaded but never used on this page.

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

About 21 KiB of CSS is downloaded but never applied on this page.

Desktop scores 81 but mobile only 43. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

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

4 KiB could be saved by minifying CSS.

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

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

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

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

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

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

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.

Your homepage downloads 4.7 MB in 171 requests on a phone: images 2.1 MB (71), fonts 1.5 MB (5) and scripts 1.1 MB (73). Under 2 MB keeps phones on slow connections fast.

3 images are downloaded at several times the size a phone draws them, for example 69702ce3cc8aeb0d7cfd644c_constellation.png at 500 px wide, shown at 61 px. Resized copies would save about 160 KiB.

11 images (482 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.

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

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

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

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

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

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

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

No XML sitemap at https://www.kicksaw.com/sitemap.xml, so Google discovers your pages only by following links.

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

The homepage links to 47 pages on kicksaw.com and 6 external pages.

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.

There is no https://www.kicksaw.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.

https://www.kicksaw.com/resources/how-baker-law-group-improved-confidential-client-support-boosted-lead-intake-and-increased-scalability and https://www.kicksaw.com/resources/from-complex-to-streamlined-scalable-truveris-journey-to-sales-procurement-solution-optimization have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.kicksaw.com/knowledge-center-blog, https://www.kicksaw.com/knowledge-center-case-studies and https://www.kicksaw.com/knowledge-center use the same meta description. A description written for each page earns more clicks.

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

2 errors were logged to the browser console while the page loaded, for example “Error: <svg> attribute width: Expected length, "auto".”.

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

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,034 words of visible text.

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.

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

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.

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