veracity-us.com website review

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

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

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

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

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

FontAwesome CDN costs a phone 5 ms of main-thread work and 300 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.

4 third-party services load with your homepage (JSDelivr CDN, FontAwesome CDN and Google Fonts and others), adding 488 KiB and 40 ms of main-thread time.

1 long task block the main thread while loading, the longest for 87 ms. During a long task the page ignores taps.

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

8 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 27.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “…”.

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

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

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

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

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

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

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

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

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

Your homepage downloads 12.6 MB in 80 requests on a phone: images 12.0 MB (49), fonts 347 KiB (11) and scripts 129 KiB (7). Under 2 MB keeps phones on slow connections fast.

veracity-ventures-logo.png weighs 1.0 MB. On a phone connection a single image that size takes seconds.

17 images (5.3 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.

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

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

4 frames have no title, so screen-reader users cannot tell what they contain.

ARIA progressbar nodes must have an accessible name: 3 elements on the page fail this check, rated serious by axe-core.

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

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

ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.

Elements marked as presentational should be consistently ignored: 2 elements on the page fail this check, rated minor by axe-core.

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 8 characters: “Veracity”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 4 <h1> headlines (“Empowering healthcare industry with IT solutions …”, “Veracity is committed to be trusted IT partner fo…” and “Empowering clients with AI driven technologies an…”). 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.

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://veracity-us.com/sitemap.xml, so Google discovers your pages only by following links.

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

There is no robots.txt at veracity-us.com/robots.txt, the first file search crawlers ask for.

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

The homepage links to 111 pages on veracity-us.com and 5 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://veracity-us.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://veracity-us.com/about, https://veracity-us.com/application-development, https://veracity-us.com/cloud, https://veracity-us.com/bpo and https://veracity-us.com/ai-ml and 10 others all use the title “Veracity”. Search engines can't tell which page to show for a search, so each competes with the others.

https://veracity-us.com/about, https://veracity-us.com/application-development, https://veracity-us.com/cloud, https://veracity-us.com/bpo, https://veracity-us.com/ai-ml and https://veracity-us.com/consulting and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://veracity-us.com/life-sciences took over 3 s to send its HTML from our server.

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

3 errors were logged to the browser console while the page loaded, for example “Failed to find a valid digest in the 'integrity' attribute for resource 'https://cdn.jsdelivr.net/npm/[email protected]/d…”.

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

3 images are served at too low a resolution for sharp phone screens.

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

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: 14 customer or partner logos. 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.

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 1,360 words of visible text.

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 5 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.