botvfx.com website review

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

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

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

16 images could be 4.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

8 third-party services load with your homepage (Google Tag Manager, Google CDN and Cloudflare CDN and others), adding 1.9 MB and 1.1 s of main-thread time.

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

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

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

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

46 KiB could be saved by minifying JavaScript.

7 KiB could be saved by minifying CSS.

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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 10.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “GET IN TOUCH”. Most of its time is element render delay (6.9 s).

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

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

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

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

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

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

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

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

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

Your homepage downloads 21.3 MB in 158 requests on a phone: media 11.7 MB (3), images 6.9 MB (88) and scripts 1.9 MB (37). Under 2 MB keeps phones on slow connections fast.

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

6 images are downloaded at several times the size a phone draws them, for example All-The-Light-We-Cannot-See.webp at 1,296 px wide, shown at 360 px. Resized copies would save about 973 KiB.

12 images (2.1 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.

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

ARIA roles used must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

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

8 images have no alt text, which hurts accessibility and image search.

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

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

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

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

There are 2 <h1> headlines (“Built on Collaboration. Powered by Value.” and “BOT VFX”). One clear main headline is easier for people and search engines.

1 link has no real href, so search engines can't follow it.

The homepage links to 32 pages on botvfx.com and 7 external pages.

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

/work, /team, /jobs, /blogs, /bot-vfx-wins-at-ficci-baf-awards-2026-for-twisted-metal-season-2 and /bot-vfx-wins-best-vfx-feature-international-for-send-help-at-vam-awards-2026 and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

/blogs and /inside-the-vfx-of-young-washington-a-bot-vfx-breakdown took over 3 s to send their HTML from our server.

We fetched 11 pages linked from your homepage and read each the way a search engine does.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

botvfx.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

botvfx.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

Your longest form asks for 12 fields (2 required). Every extra field lowers completion.

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

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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