internationalcomputing.com website review

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

31 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.6 s faster on a phone.

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

About 500 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 2.1 s faster on a phone.

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

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

8 third-party services load with your homepage (Google Tag Manager, jQuery CDN and Cloudflare CDN and others), adding 3.9 MB and 560 ms of main-thread time.

110 KiB could be saved by minifying JavaScript.

Amazon Web Services costs a phone 32 ms of main-thread work and 3.2 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.

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

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

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

101 KiB could be saved by minifying CSS.

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

Polyfills for old browsers add 8 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.

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

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

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

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

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

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

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.1 MB in 82 requests on a phone: images 2.6 MB (41), scripts 815 KiB (27) and stylesheets 528 KiB (7). Under 2 MB keeps phones on slow connections fast.

10 images are downloaded at several times the size a phone draws them, for example Predictive-Logistics-Plain.png at 1,653 px wide, shown at 308 px. Resized copies would save about 1.3 MB.

Predictive-Logistics-Plain.png weighs 550 KiB. On a phone connection a single image that size takes seconds.

15 images (2.3 MB) 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.

13 images further down the page (1.8 MB) 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 1.15 g of CO₂e: 137.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 button has no accessible name, so screen readers announce just “button”.

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

Documents must have <title> element to aid in navigation: 1 element on the page fails this check, rated serious by axe-core.

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

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

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

Your page has no <title>, so Google has to invent the blue link in search results.

There is no <h1>, so neither visitors nor Google get a clear main headline.

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 251 characters; Google truncates after about 160, so the end of your pitch is cut.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 132 pages on internationalcomputing.com and 4 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.

https://www.internationalcomputing.com/transformation-toolbox, https://www.internationalcomputing.com/transformation-toolbox/integration-options, https://www.internationalcomputing.com/transformation-toolbox/software-as2-edi, https://www.internationalcomputing.com/transformation-toolbox/portal-options, https://www.internationalcomputing.com/transformation-toolbox/delivering-outcomes and https://www.internationalcomputing.com/transformation-toolbox/service-fundamentals and 9 others have no <title>, so Google invents the link text in results.

https://www.internationalcomputing.com/services/integration-competency-center, https://www.internationalcomputing.com/enterprise-integration, https://www.internationalcomputing.com/aws-consulting and https://www.internationalcomputing.com/enterprise-integration-hub use the same meta description. A description written for each page earns more clicks.

https://www.internationalcomputing.com/transformation-toolbox, https://www.internationalcomputing.com/transformation-toolbox/integration-options, https://www.internationalcomputing.com/transformation-toolbox/software-as2-edi, https://www.internationalcomputing.com/transformation-toolbox/portal-options, https://www.internationalcomputing.com/transformation-toolbox/delivering-outcomes and https://www.internationalcomputing.com/transformation-toolbox/service-fundamentals and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

3 of 9 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 “Cannot read properties of null (reading 'addEventListener')”.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and X (Twitter) Ads (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 8 cookies, 2 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 12 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.