Programmable

Website review, no card needed

outpost-vfx.com logo

outpost-vfx.com website review

Visit site (opens in a new tab)Reviewed 5 November 202629 issues · 68 checks

This review found 29 issues worth fixing on outpost-vfx.com, 9 of them high impact, across 68 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Site score

79C

Closest competitors among reviewed websites

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
2.5 s1.7 sMay 16Oct 312.3 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.2 s
May 23, 20261.9 s
Jun 13, 20261.8 s
Jun 20, 20261.9 s
Jun 27, 20262.1 s
Jul 4, 20262.2 s
Jul 11, 20262.4 s
Jul 18, 20262.2 s
Oct 10, 20262.3 s
Oct 17, 20262.2 s
Oct 24, 20262.1 s
Oct 31, 20262.3 s
Real-visitor tap response (INP)75th percentile, phones
124 ms106 msJun 13Oct 31122 ms
Show as table
DateReal-visitor tap response (INP)
Jun 13, 2026108 ms
Jun 20, 2026113 ms
Jun 27, 2026120 ms
Jul 4, 2026118 ms
Jul 11, 2026118 ms
Oct 17, 2026122 ms
Oct 24, 2026122 ms
Oct 31, 2026122 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

outpost-vfx.com (opens in a new tab)
Full-page screenshot of outpost-vfx.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. outpost-vfx.com at 0.4 s0.4 s
  2. outpost-vfx.com at 0.8 s0.8 s
  3. outpost-vfx.com at 1.1 s1.1 s
  4. outpost-vfx.com at 1.5 s1.5 s
  5. outpost-vfx.com at 1.9 s1.9 s
  6. outpost-vfx.com at 2.3 s2.3 s
  7. outpost-vfx.com at 2.6 s2.6 s
  8. outpost-vfx.com at 3.0 s3.0 s

Speed

7 to fix79

  • Use efficient cache lifetimes

    1.1 s · 803 KiB

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

  • Render-blocking requests

    1.2 s

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

  • Improve image delivery

    800 ms · 853 KiB

    4 images could be 853 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 800 ms faster on a phone.

  • Mobile performance score: 79

    79/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Hotjar and jQuery CDN and others), adding 665 KiB and 525 ms of main-thread time.

  • Reduce unused JavaScript

    160 ms · 376 KiB

    About 376 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 160 ms faster on a phone.

  • Google Tag Manager adds 378 ms

    378 ms

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

  • 5 long tasks on the main thread

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

  • Reduce unused CSS

    160 ms · 30 KiB

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

  • Font display

    50 ms

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

  • Chained critical requests

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

2 checks passed

  • Main-thread work: 1.1 s

    A phone's processor spends 1.1 s on main-thread work while loading, 496 ms of it running JavaScript. That is comfortably low.

  • Server response: 2 ms

    2 ms

    Your server sent the HTML in 2 ms, well inside Google's 600 ms guideline.

Core Web Vitals

8 to fix50

  • Fails Core Web Vitals for real visitors

    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-user CLS: 0.26

    0.26

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

  • Time to Interactive: 9.0 s

    9.0 s

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

  • Largest Contentful Paint: 4.5 s

    4.5 s

    Your largest element takes 4.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Outpost VFX creates stunning visual effects for film and ep…”.

  • Real-user TTFB: 973 ms

    973 ms

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

  • Speed Index: 4.2 s

    4.2 s

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

  • First Contentful Paint: 2.0 s

    2.0 s

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

  • 14 images without width and height

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

  • Tap response (INP) got 10% slower for real visitors

    +10%

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

  • Largest content (LCP) held steady for real visitors

    +9%

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

4 checks passed

  • Real-user LCP: 2.2 s

    2.2 s

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

  • Real-user FCP: 1.6 s

    1.6 s

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

  • Total Blocking Time: 126 ms

    126 ms

    Scripts block the page for only 126 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

100

  • About 0.6 g of CO₂ per visit

    0.55 g

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

1 checks passed

  • Page weight: 2.0 MB in 40 requests

    2.0 MB

    Your homepage downloads 2.0 MB in 40 requests on a phone: images 1.1 MB (11), scripts 727 KiB (16) and fonts 49 KiB (1). That is a lean page.

Accessibility

4 to fix78

  • Invalid ARIA attributes

    1 element use ARIA attributes their role does not allow, which confuses screen readers.

  • 5 links without text

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

  • 3 text elements with low contrast

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

  • No page language

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

  • Elements with visible text labels do not have matching accessible names.

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

1 checks passed

  • Every image has alt text

    All 17 images in the HTML carry an alt attribute.

SEO

4 to fixGoogle 8580

  • No H1 headline

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

  • Meta description is long (211 characters)

    Your meta description is 211 characters; Google truncates after about 160, so the end of your pitch is cut.

  • No social preview image

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

  • 2 links crawlers can't follow

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

  • No X (Twitter) card tag

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

  • 49 internal links, 6 external

    The homepage links to 49 pages on outpost-vfx.com and 6 external pages.

5 checks passed

  • Title: 53 characters

    Your title is a healthy 53 characters: “Visual effects for film and high-end TV | Outpost VFX”.

  • Canonical URL set

    The canonical URL is https://www.outpost-vfx.com/.

  • Structured data in place

    Structured data found: Organization.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://outpost-vfx.com/sitemap.xml.

AI search readiness

100

  • No llms.txt

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

2 checks passed

  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

Other pages

4 to fix76

  • 14 pages point its canonical at the homepage

    https://outpost-vfx.com/careers, https://outpost-vfx.com/en/reels, https://outpost-vfx.com/work, https://outpost-vfx.com/news, https://outpost-vfx.com/about and https://outpost-vfx.com/contact and 8 others declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.

  • 8 pages share a title

    https://outpost-vfx.com/en, /, https://outpost-vfx.com/en/news/emmys-2026-outpost-vfx-nominated-for-outstanding-special-visual-effects-for-foundation-season-3, https://outpost-vfx.com/en/work/the-dog-stars, https://outpost-vfx.com/en/news/fmx-2026-outpost-vfx-talks-ai-cloud-and-comp-alongside-aws-and-foundry and https://outpost-vfx.com/en/news/oscars-nominations-2026-sinners-and-the-lost-bus-up-for-best-vfx and 2 others all use the title “Visual effects for film and high-end TV | Outpost VFX”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 7 pages share a meta description

    /, https://outpost-vfx.com/about, https://outpost-vfx.com/en/news/emmys-2026-outpost-vfx-nominated-for-outstanding-special-visual-effects-for-foundation-season-3, https://outpost-vfx.com/en/work/the-dog-stars, https://outpost-vfx.com/en/news/fmx-2026-outpost-vfx-talks-ai-cloud-and-comp-alongside-aws-and-foundry and https://outpost-vfx.com/en/news/oscars-nominations-2026-sinners-and-the-lost-bus-up-for-best-vfx and 1 other use the same meta description. A description written for each page earns more clicks.

  • 2 pages without an H1

    / and https://outpost-vfx.com/careers have no <h1> headline, so visitors and search engines get no clear main topic.

  • 5 pages with very little text

    https://outpost-vfx.com/en/reels, https://outpost-vfx.com/work, https://outpost-vfx.com/news, https://outpost-vfx.com/en/work/the-dog-stars and https://outpost-vfx.com/en/work/silo-s3 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.

  • 15 internal pages checked

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

4 checks passed

  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693

  • 1 console error

    1 error was logged to the browser console during Google's test (“Failed to load resource: net::ERR_CONNECTION_FAILED”).

1 checks passed

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix88

  • No direct contact details

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

  • No form on the homepage

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

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

  • About 287 words of copy

    The homepage carries about 287 words of visible text.

3 checks passed

  • 4 calls to action

    The homepage has 4 calls to action, for example “Contact” and “Sign up”.

  • Social proof on the page

    Social proof on the homepage: 1 testimonial or review block and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Hotjar.

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at outpost-vfx.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
jQuery
Analytics
Google Analytics | Google Tag Manager | Hotjar
Hosting
Cloudflare

Hiring

Hiring
23 open roles
Teams
Compositing (3), FX (3), Animation (2), Assets (2)
Job board
smartrecruiters
Careers page
outpost-vfx.com/en/careers (opens in a new tab)

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 29 issues on outpost-vfx.com, including 15 speed issues, 4 SEO issues and 1 conversion gap. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25