veritaspress.com website review

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

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

8 images could be 1.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 600 ms faster on a phone.

8 third-party services load with your homepage (Google Tag Manager, Facebook and Hubspot and others), adding 1.3 MB and 1.3 s of main-thread time.

Your mobile performance score is 50 (desktop: 87). Pages that score under 90 lose visitors before the first paint.

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

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

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

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

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

About 140 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).

15 KiB could be saved by minifying CSS.

Desktop scores 87 but mobile only 50. A gap that wide usually means heavy scripts and images that hit phones hardest.

7 KiB could be saved by minifying JavaScript.

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.

Your largest element takes 16.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Classical Christian Education That Prepares Your Child for …”.

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

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

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

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

Real visitors wait 1.2 s for your server to start answering (75th percentile). Good is under 800 ms.

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

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

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

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.5 s to 2.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 16.3 MB in 103 requests on a phone: media 13.0 MB (3), images 1.6 MB (18) and scripts 1.4 MB (41). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example media.nl at 625 px wide, shown at 140 px. Resized copies would save about 32 KiB.

2 images (123 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.

1 image further down the page (65 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

Elements with visible text labels do not have matching accessible names. (1 element).

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

The homepage links to 83 pages on veritaspress.com and 35 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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

https://veritaspress.com/choose-your-curriculum, https://veritaspress.com/selfpaced, https://veritaspress.com/selfpaced/history, https://veritaspress.com/selfpaced/bible, https://veritaspress.com/selfpaced/omnibus and https://veritaspress.com/selfpaced/rhetoric and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

https://veritaspress.com/choose-your-curriculum, https://veritaspress.com/selfpaced, https://veritaspress.com/selfpaced/history, https://veritaspress.com/selfpaced/bible, https://veritaspress.com/selfpaced/omnibus and https://veritaspress.com/selfpaced/rhetoric and 9 others have 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 50 found) and read each the way a search engine does.

2 images failed to load on a phone, for example https://veritaspress.com/images/minicart.svg.

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

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.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and Meta Pixel and 4 mores (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 23 cookies, 2 of them by other companies (measured from a US location before any click).

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