phaseone.com website review

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

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

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

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

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

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

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

About 240 KiB of JavaScript is downloaded but never used on this page.

6 third-party services load with your homepage (Google Tag Manager, cookieinformation.com and JSDelivr CDN and others), adding 451 KiB and 119 ms of main-thread time.

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

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

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

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

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

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

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

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

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

The layout shifts by 0.209 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

15 images 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 109 ms to 109 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-10-24, 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).

Your homepage downloads 4.6 MB in 60 requests on a phone: images 3.5 MB (31), scripts 597 KiB (13) and fonts 289 KiB (6). Under 2 MB keeps phones on slow connections fast.

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

3 images are downloaded at several times the size a phone draws them, for example Quantum_Spatial_samples_for_PO0006-2400x1350.jpg at 2,400 px wide, shown at 390 px. Resized copies would save about 2.1 MB.

Quantum_Spatial_samples_for_PO0006-2400x1350.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

10 images further down the page (340 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

1 image (39 KiB) is 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.

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

5 buttons have no accessible name, so screen readers announce just “button”.

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

Heading levels should only increase by one: 3 elements on the page fail this check, rated moderate by axe-core.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 3 elements on the page fail this check, rated moderate by axe-core.

Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one contentinfo landmark: 1 element on the page fails 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.

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

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

There are 11 <h1> headlines (“Introducing the Next Generation of Phase One Aeri…”, “250MP single shot imaging system capable of A0 at…” and “iX Process — now available for our camera compone…”). One clear main headline is easier for people and search engines.

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

The homepage links to 92 pages on phaseone.com and 11 external pages.

https://www.phaseone.com/contact-us-form has no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.phaseone.com/contact-us-form, whose canonical is https://www.phaseone.com/contact-us-phase-one. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.phaseone.com/contact-us-form has no <h1> headline, so visitors and search engines get no clear main topic.

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

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://use.fontawesome.com/releases/v6.5.1/css/all.css?ver=7.1.3' from origin 'https://ww…”.

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

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.

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.

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

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