vcoe.org website review

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

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

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

audioeye.com costs a phone 1.5 s of main-thread work and 297 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

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

8 third-party services load with your homepage (audioeye.com, Google Tag Manager and Other Google APIs/SDKs and others), adding 1,000 KiB and 2.1 s of main-thread time.

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

42 KiB could be saved by minifying JavaScript.

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

Google Tag Manager costs a phone 269 ms of main-thread work and 285 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 2,675 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

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

16 KiB could be saved by minifying CSS.

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.

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.

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

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

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

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

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

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

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

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

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

Your homepage downloads 6.6 MB in 101 requests on a phone: images 4.7 MB (36), scripts 1.4 MB (30) and stylesheets 194 KiB (23). Under 2 MB keeps phones on slow connections fast.

3 images weigh 3.1 MB together. On a phone connection a single image that size takes seconds.

3 images are downloaded at several times the size a phone draws them, for example golden-bell.jpg at 1,400 px wide, shown at 390 px. Resized copies would save about 500 KiB.

9 images (4.0 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.

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

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

Some lists contain elements other than list items, which screen readers announce wrongly.

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

5 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

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.

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.vcoe.org/sitemap.xml, so Google discovers your pages only by following links.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

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

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

The homepage links to 463 pages on vcoe.org and 51 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.

There is no https://www.vcoe.org/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.vcoe.org/Educators, https://www.vcoe.org/Programs-Services, https://www.vcoe.org/cec, https://www.vcoe.org/charter, https://www.vcoe.org/Communications and https://www.vcoe.org/cpsa and 9 others use the same meta description. A description written for each page earns more clicks.

https://www.vcoe.org/Educators, https://www.vcoe.org/Programs-Services, https://www.vcoe.org/cec, https://www.vcoe.org/charter, https://www.vcoe.org/Communications and https://www.vcoe.org/cpsa and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.

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

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 (Not Found)”.

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

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.

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

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