inhouseincorp.com website review

132 files are served with short cache lifetimes, so returning visitors download them again (1.7 MB).

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

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

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

8 third-party services load with your homepage (YouTube, Google Tag Manager and trustindex.io and others), adding 1.4 MB and 649 ms of main-thread time.

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

The HTML itself could arrive about 650 ms sooner: redirects, a slow server response or missing compression delay everything after it.

Reduce initial server response time. Google estimates savings of 638 ms on a phone.

YouTube costs a phone 445 ms of main-thread work and 975 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.

5 images could be 228 KiB 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.

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

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

Your server takes 738 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.

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

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

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

20 KiB could be saved by minifying JavaScript.

19 KiB could be saved by minifying CSS.

Desktop scores 87 but mobile only 58. 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.

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

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

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

Your largest element takes 5.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We are here to serve the whole new solutions for Strategic …”. Most of its time is element render delay (2.5 s).

2 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 3.1 MB in 175 requests on a phone: scripts 1.4 MB (51), fonts 715 KiB (16) and images 579 KiB (25). Under 2 MB keeps phones on slow connections fast.

inhouse-aboutus-1-e1650283469166-pvjwr8e28dl3i8wvtelsi4f3gxu is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

3 images (352 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 further down the page (82 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

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

3 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: 130 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.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.

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

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

Your title is 110 characters, so Google will cut it off around 60: “InHouse - Trusted Partner for Strategic Sourcing, Quality Assurance, Supplier Management …”.

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

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

The homepage links to 77 pages on inhouseincorp.com and 15 external pages.

There is no https://www.inhouseincorp.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.inhouseincorp.com/container-loading-inspection and https://www.inhouseincorp.com/supplier-performance-improvement took over 3 s to send their HTML from our server.

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

2 images failed to load on a phone, for example https://nimeshdetroja.co.in/inhouse/wp-content/uploads/2022/03/Logo-2.png.

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

6 errors were logged to the browser console while the page loaded, for example “Mixed Content: The page at 'https://www.inhouseincorp.com/' was loaded over HTTPS, but requested an insecure font 'http…”.

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

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.

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.

The homepage carries about 542 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, 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 4 cookies, 1 of them by other companies (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 16 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.