vectorbuilder.com website review

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

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

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

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

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

11 long tasks block the main thread while loading, the longest for 1.9 s. During a long task the page ignores taps.

8 third-party services load with your homepage (Google Tag Manager, Clarity and Hubspot and others), adding 770 KiB and 921 ms of main-thread time.

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

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

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

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

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.

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

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

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

Your largest element takes 35.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

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

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

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

Real visitors wait 329 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

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

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

Your homepage downloads 7.4 MB in 101 requests on a phone: images 4.0 MB (54), scripts 3.1 MB (20) and stylesheets 105 KiB (2). Under 2 MB keeps phones on slow connections fast.

2 images weigh 2.8 MB together. On a phone connection a single image that size takes seconds.

4 images are downloaded at several times the size a phone draws them, for example VectorBuilder.8df33cc4d92cc157706c14daa756e0ad.gif at 2,015 px wide, shown at 205 px. Resized copies would save about 1.2 MB.

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

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

Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.

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

<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

Main landmark should not be contained in another landmark: 8 elements on the page fail this check, rated moderate by axe-core.

All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.

Document should not have more than one main 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.

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.

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

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is 68 characters, so Google will cut it off around 60: “VectorBuilder | Revolutionize Gene Delivery from Research to Therapy”.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

13 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.

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

The homepage links to 230 pages on vectorbuilder.com and 16 external pages.

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

robots.txt blocks GPTBot and ClaudeBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

https://en.vectorbuilder.com/design/retrieve.html, https://en.vectorbuilder.com/design/retrieve/proposal.html, https://en.vectorbuilder.com/dealer/territory/users.html, https://en.vectorbuilder.com/dealer/territory/quotes.html, https://en.vectorbuilder.com/dealer/territory/orders.html and https://en.vectorbuilder.com/dealer/territory/shipments.html and 5 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://en.vectorbuilder.com/design/retrieve.html, https://en.vectorbuilder.com/design/retrieve/proposal.html, https://en.vectorbuilder.com/dealer/territory/users.html, https://en.vectorbuilder.com/dealer/territory/quotes.html, https://en.vectorbuilder.com/dealer/territory/orders.html and https://en.vectorbuilder.com/dealer/territory/shipments.html and 5 others all use the title “Verifying...”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://en.vectorbuilder.com/design/retrieve.html, https://en.vectorbuilder.com/design/retrieve/proposal.html, https://en.vectorbuilder.com/dealer/territory/users.html, https://en.vectorbuilder.com/dealer/territory/quotes.html, https://en.vectorbuilder.com/dealer/territory/orders.html and https://en.vectorbuilder.com/dealer/territory/shipments.html and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://en.vectorbuilder.com/resources/submit-materials.html, https://en.vectorbuilder.com/resources/place-order.html, https://en.vectorbuilder.com/resources/track-shipment.html and https://en.vectorbuilder.com/resources/retrieve-coa.html use the same meta description. A description written for each page earns more clicks.

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

No viewport meta tag, so phones render the desktop layout zoomed out.

3 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=97109400&tm=gtm002&Ver=2&mid=3b335bd8-d900-45e9-8397-4796824e66e4&bo=1&sid=276e4000cb5311f18be2138cd57f2680&vid=276e4940cb5311f1a822615c3183ee4c&vids=1&msclkid=N&gtm_t.

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

Large scripts ship without source maps.

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

Social proof on the homepage: 4 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

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

There is no form on the homepage, so every lead has to click through to another page first.

The homepage carries about 397 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and LinkedIn Insight and 3 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 22 cookies (measured from a US location before any click).

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