phrasea.com website review

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

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

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

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

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

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

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

23 KiB could be saved by minifying CSS.

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

1 third-party service load with your homepage (Google Fonts), adding 79 KiB and 2 ms of main-thread time.

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

1 image could be 5 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

Your largest element takes 4.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Phrasea the Open Source DAM Built on over 30 years of exper…”.

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

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

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

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

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.

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

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

3 frames have no title, so screen-reader users cannot tell what they contain.

1 link inside paragraphs relies on colour alone to stand out.

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

Elements with role="dialog" or role="alertdialog" do not have accessible names. (1 element).

Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.

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

Structured data found (Organization and SoftwareApplication) but with 1 problem, for example “SoftwareApplication: no offers (price) block”.

The homepage links to 25 pages on phrasea.com and 12 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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

https://www.phrasea.com/en/support, https://www.phrasea.com/en/mentionslegales and https://www.phrasea.com/en/cookie-policy are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://www.phrasea.com/en/contactus and https://www.phrasea.com/en/cookie-policy have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.phrasea.com/en/demo, https://www.phrasea.com/en/features and https://www.phrasea.com/en/cookie-policy have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.phrasea.com/en/contactus has 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.

We fetched 10 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_UNKNOWN_URL_SCHEME”.

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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust 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 445 words of visible text.

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 2 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.