questinc.com website review

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

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

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

3 third-party services load with your homepage (Vimeo, Cloudflare CDN and Google Fonts), adding 4.7 MB and 227 ms of main-thread time.

Vimeo costs a phone 222 ms of main-thread work and 4.4 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.

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

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

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

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

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

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.

4 KiB could be saved by minifying CSS.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

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

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

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

Your largest element takes 4.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Leverage Quest's world-class depot repair infrastructure an…”. Most of its time is element render delay (2.5 s).

Real visitors wait 3.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.

For real visitors the layout shifts by 0.11 (75th percentile). Good is under 0.1.

Real visitors see the first content after 2.0 s (75th percentile). Good is under 1.8 s.

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

Your homepage downloads 5.2 MB in 100 requests on a phone: other files 3.3 MB (42), scripts 1.1 MB (18) and fonts 432 KiB (5). Under 2 MB keeps phones on slow connections fast.

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

3 links inside paragraphs rely on colour alone to stand out.

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

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

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

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

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

1 link has no real href, so search engines can't follow it.

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

The homepage links to 72 pages on questinc.com and 5 external pages.

https://www.questinc.com/index declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

/ and https://www.questinc.com/index all use the title “Global Post-Sales Service and IT Solutions | Quest International”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.questinc.com/search-results 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 63 found) and read each the way a search engine does.

3 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

3 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'addEventListener')”.

3 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

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

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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.

Social proof on the homepage: 30 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

Opening the homepage sets 2 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.