invints.com website review

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

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

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

Your mobile performance score is 57 (desktop: 91). Pages that score under 90 lose visitors before the first paint.

20 images could be 537 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 250 ms faster on a phone.

8 third-party services load with your homepage (Google Tag Manager, Facebook and Clarity and others), adding 844 KiB and 657 ms of main-thread time.

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

13 KiB could be saved by minifying CSS.

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

14 KiB could be saved by minifying JavaScript.

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

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

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

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

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.

Your largest element takes 13.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “6000+ PIXEL-PERFECT PROJECTS DELIVERED TO 4000+ HAPPY CUSTO…”.

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

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

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

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

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

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 2.4 MB in 130 requests on a phone: scripts 1.0 MB (22), images 1.0 MB (76) and fonts 224 KiB (4). Under 2 MB keeps phones on slow connections fast.

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

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

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

4 images have no alt text, which hurts accessibility and image search.

All page content should be contained by landmarks: 36 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.

7 visible links have no text or label, so screen readers cannot say where they go.

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

ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.

Elements marked as presentational should be consistently ignored: 2 elements on the page fail this check, rated minor by axe-core.

Headings skip levels (h1 → h4, h4 → h6 and h2 → h6), 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.

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

6 links have no real href, so search engines can't follow them.

The homepage links to 46 pages on invints.com and 14 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://invints.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://invints.com/shopify-ecommerce.html, https://invints.com/digital-product-development.html, https://invints.com/marketing-design-and-animation.html and https://invints.com/digital-marketing.html all use the title “Leading eCommerce Agency | Invints Ecommerce Solutions”. Search engines can't tell which page to show for a search, so each competes with the others.

https://invints.com/shopify-development-agency.html, https://invints.com/shopify-ecommerce.html, https://invints.com/digital-product-development.html, https://invints.com/branding-services.html, https://invints.com/marketing-design-and-animation.html and https://invints.com/digital-marketing.html use the same meta description. A description written for each page earns more clicks.

Your homepage links to 13 pages by a URL that isn't their canonical one, for example https://invints.com/our-projects, whose canonical is https://invints.com/our-projects.html. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://invints.com/our-projects and https://invints.com/about-us.html have no <h1> headline, so visitors and search engines get no clear main topic.

https://invints.com/our-projects has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

6 images failed to load on a phone, for example https://invints.com/assets/images/mega_menu_arrow.webp.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

2 errors were logged to the browser console while the page loaded, for example “loadMore is not defined”.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel and 1 more (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 6 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 17 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.