valicor.com website review

About 1.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.5 s faster on a phone.

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

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

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

8 third-party services load with your homepage (Google CDN, Google Tag Manager and hsappstatic.net and others), adding 3.3 MB and 2.4 s of main-thread time.

Google CDN costs a phone 657 ms of main-thread work and 1.1 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.

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

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

hsappstatic.net costs a phone 442 ms of main-thread work and 1.0 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.

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

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

CallRail costs a phone 276 ms of main-thread work and 13 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.

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

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

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

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.

3 KiB could be saved by minifying CSS.

1 KiB JavaScript is shipped twice across bundles.

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

Your largest element takes 13.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “EACH YEAR VALICOR RECYCLES AND REPURPOSES 400 + MILLION GAL…”.

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

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

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

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 149 ms to 188 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 13.8 MB in 133 requests on a phone: media 9.2 MB (3), scripts 3.3 MB (47) and other files 392 KiB (28). Under 2 MB keeps phones on slow connections fast.

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

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

Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

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.

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

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

The homepage links to 212 pages on valicor.com and 3 external pages.

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

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

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

2 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 “Failed to load resource: net::ERR_FAILED”.

Large scripts ship without source maps.

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

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

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.

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

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

Opening the homepage sets 15 cookies (measured from a US location before any click).

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