veritivvisual.com website review

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

8 third-party services load with your homepage (YouTube, Google Tag Manager and Hotjar and others), adding 2.0 MB and 1.5 s of main-thread time.

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

About 994 KiB of JavaScript is downloaded but never used on this page.

7 images could be 596 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.

YouTube costs a phone 492 ms of main-thread work and 1,006 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.

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

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

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

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

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

About 136 KiB of CSS is downloaded but never applied on this page.

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

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

The page becomes fully interactive after 25.0 s. Good is under 3.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 image.

Scripts block taps and scrolling for 1.0 s 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 4.2 MB in 142 requests on a phone: scripts 2.1 MB (46), images 1.1 MB (20) and fonts 668 KiB (9). Under 2 MB keeps phones on slow connections fast.

Orora-Visual-creative-services-2-768x336.jpg 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).

7 images (825 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.

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

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

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

1 visible link has no text or label, so screen readers cannot say where it goes.

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

The robots meta tag says “noindex, follow”: Google is told not to list this page at all.

Google's crawler is blocked from indexing this page.

Your title is only 21 characters: “Home - Veritiv Visual”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 3 <h1> headlines (“In-Store Marketing Solutions”, “In-Store Marketing Solutions” and “Experts in Visual Communication”). One clear main headline is easier for people and search engines.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

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

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

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

The homepage links to 113 pages on veritivvisual.com and 69 external pages.

There is no https://veritivvisual.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.

Your homepage links to https://veritivvisual.com/veritiv-rebranding-services, https://veritivvisual.com/expertise/design-innovation, https://veritivvisual.com/expertise/packaging-prototyping-and-testing, https://veritivvisual.com/expertise/product-retail-marketing, https://veritivvisual.com/expertise/corrugated-manufacturing and https://veritivvisual.com/expertise/contract-packaging-fulfillment and 6 others, which answer with an error. Visitors hit a dead end and search engines drop them.

https://veritivvisual.com/get-started, https://veritivvisual.com/markets and https://veritivvisual.com/print are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://veritivvisual.com/markets and https://veritivvisual.com/print have no meta description, so Google writes the search snippet from whatever text it finds.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=187073254&Ver=2&mid=4a66754d-be55-464a-9084-3cb2686d9095&bo=1&sid=11581370d55711f18bb8737893b8fd83&vid=11585290d55711f188b8e379f43bc031&vids=1&msclkid=N&pi=918639831&l.

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

1 error was logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'c')”.

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: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and LinkedIn Insight and 3 mores (measured from a US location before any click). A consent tool (TrustArc) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 15 cookies, 1 of them by other companies (measured from a US location before any click).

Loading the homepage contacts 26 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.