Website review, no card needed

fovia.com logo

fovia.com website review

Visit site (opens in a new tab)Reviewed 21 November 202641 issues · 84 checks

This review found 41 issues worth fixing on fovia.com, 17 of them high impact, across 84 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

Full-page screenshot of fovia.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. fovia.com at 0.8 s0.8 s
  2. fovia.com at 1.5 s1.5 s
  3. fovia.com at 2.3 s2.3 s
  4. fovia.com at 3.0 s3.0 s
  5. fovia.com at 3.8 s3.8 s
  6. fovia.com at 4.6 s4.6 s
  7. fovia.com at 5.3 s5.3 s
  8. fovia.com at 6.1 s6.1 s

Speed

10 to fix55
  • Use efficient cache lifetimes

    9.5 s · 4.2 MB

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

  • Reduce unused JavaScript

    9.3 s · 1.8 MB

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

  • Render-blocking requests

    10.8 s

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

  • Reduce unused CSS

    2.2 s · 757 KiB

    About 757 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 2.2 s faster on a phone.

  • Improve image delivery

    1.1 s · 897 KiB

    7 images could be 897 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.

  • Minify JavaScript

    1.5 s · 271 KiB

    271 KiB could be saved by minifying JavaScript.

  • Mobile performance score: 55

    55/100

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

  • Legacy JavaScript

    450 ms · 92 KiB

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

  • Document request latency

    520 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

  • 1,667 HTML elements

    The page has 1,667 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Minify CSS

    230 ms · 43 KiB

    43 KiB could be saved by minifying CSS.

  • 3 third-party services on the page

    3 third-party services load with your homepage (Google Tag Manager, Google Analytics and Google Fonts), adding 206 KiB and 144 ms of main-thread time.

  • 3 long tasks on the main thread

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

  • 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.6 s

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

  • Server response: 380 ms

    380 ms

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

Core Web Vitals

4 to fix67
  • First Contentful Paint: 16.4 s

    16.4 s

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

  • Largest Contentful Paint: 54.1 s

    54.1 s

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

  • Speed Index: 20.2 s

    20.2 s

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

  • Time to Interactive: 55.9 s

    55.9 s

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

2 checks passed
  • Cumulative Layout Shift: 0.002

    0.002

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

  • Total Blocking Time: 27 ms

    27 ms

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

Images and page weight

5 to fix18
  • Page weight: 11.8 MB in 122 requests

    11.8 MB

    Your homepage downloads 11.8 MB in 122 requests on a phone: images 7.9 MB (60), scripts 2.7 MB (35) and HTML 780 KiB (2). Under 2 MB keeps phones on slow connections fast.

  • 2 images over 500 KB

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

  • 15 images far larger than shown

    1.5 MB

    15 images are downloaded at several times the size a phone draws them, for example MakevsBuy_fovia.png at 1,108 px wide, shown at 246 px. Resized copies would save about 1.5 MB.

  • 40 images in older formats

    40 images (7.6 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.

  • 13 images below the first screen load straight away

    13 images further down the page (2.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 3.3 g of CO₂ per visit

    3.33 g

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

Accessibility

7 to fixGoogle 8589
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 7 tap targets too small

    7 tap targets are too small or too close together to hit reliably with a finger.

  • 1 text element with low contrast

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

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • Contentinfo landmark should not be contained in another landmark (1 element)

    Contentinfo landmark should not be contained in another 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)

    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.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

2 checks passed
  • Every image has alt text

    All 107 images in the HTML carry an alt attribute.

  • 42 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 8591
  • 2 H1 headlines

    There are 2 <h1> headlines (“Home Page Fovia” and “Contact Information”). One clear main headline is easier for people and search engines.

  • 1 link crawlers can't follow

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

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 99 internal links, 3 external

    The homepage links to 99 pages on fovia.com and 3 external pages.

7 checks passed
  • Meta description: 152 characters

    Your meta description is 152 characters: “Explore Fovia's 3D Visualization Software. We help you develop medical imaging software for 3D applications with our aw…”.

  • Title: 46 characters

    Your title is a healthy 46 characters: “Fovia Advanced Visualization Software Platform”.

  • Canonical URL set

    The canonical URL is https://fovia.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, WebPage and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://fovia.com/sitemap.xml.

AI search readiness

1 to fix88
  • No Organization structured data

    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.

  • No llms.txt

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

  • Text is in the HTML

    Your server sends the page's text in the HTML (829 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix81
  • 6 pages share 3 titles

    https://fovia.com/about-us and https://fovia.com/index.php/about-us all use the title “About Fovia, 3D Medical Imaging Solution Provider”, and 2 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages without a meta description

    https://fovia.com/markets and https://fovia.com/faq have no meta description, so Google writes the search snippet from whatever text it finds.

  • 6 pages share a meta description

    https://fovia.com/about-us and https://fovia.com/index.php/about-us use the same meta description. A description written for each page earns more clicks.

  • 2 links to non-canonical URLs

    Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://fovia.com/index.php/about-us, whose canonical is https://fovia.com/about-us. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 4 pages slow to respond

    https://fovia.com/index.php/about-us, https://fovia.com/markets, https://fovia.com/advisors and https://fovia.com/index.php/xstream-hdvr-product-overview took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 58 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 an H1

    Each page we checked has a main headline.

  • 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

3 to fixGoogle 7385
  • 9 small tap targets

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

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “WebSocket connection to 'wss://3d.fovia.com:8088/socket.io/?EIO=3&transport=websocket' failed: Establishing a tunnel vi…”.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix81
  • Local business without LocalBusiness data

    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.

  • Thin social proof

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

  • 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 opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • 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 275 words of copy

    The homepage carries about 275 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Schedule a Meeting ~ RSNA 2026”.

  • 34 calls to action

    The homepage has 34 calls to action, for example “Contact Us”, “Make vs. Buy” and “Learn More”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Phone number on the homepage

    Your phone number is on the homepage.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    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.

  • 4 cookies set on arrival

    4

    Opening the homepage sets 4 cookies (measured from a US location before any click).

  • No consent tool detected

    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.

  • 5 other companies contacted

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

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 fovia.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Analytics
Hosting
InMotion Hosting, Inc.

Company

Headquarters
Palo Alto

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 41 issues on fovia.com, including 14 speed issues, 3 SEO issues and 3 conversion gaps. 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