squadinventive.com website review

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

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

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

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

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

About 23 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 130 ms faster on a phone.

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

4 images could be 35 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

Your largest element takes 4.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Engineering Digital Products That Transform Businesses”. Most of its time is element render delay (2.5 s).

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

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

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.

myanpa.png weighs 600 KiB. On a phone connection a single image that size takes seconds.

1 image (600 KiB) is 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 0.32 g of CO₂e: 39.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

5 tap targets are too small or too close together to hit reliably with a finger.

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.

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

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

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

There is no robots.txt at squadinventive.com/robots.txt, the first file search crawlers ask for.

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

The homepage links to 76 pages on squadinventive.com and 13 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 /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.

/, /company/who-we-are, /our-services, /products, /portfolio and /blog and 10 others all use the title “Squad Inventive — Custom Software Development Agency”. Search engines can't tell which page to show for a search, so each competes with the others.

/company/who-we-are, /our-services, /products, /portfolio, /blog and /contact-us and 9 others use the same meta description. A description written for each page earns more clicks.

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

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 analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

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

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

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.