platform1online.com website review

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

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

Your mobile performance score is 61 (desktop: 87). Pages that score under 90 lose visitors before the first paint.

5 third-party services load with your homepage (website-files.com, cloudfront.net and Google CDN and others), adding 3.2 MB and 138 ms of main-thread time.

website-files.com costs a phone 114 ms of main-thread work and 3.0 MB 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 32 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

Desktop scores 87 but mobile only 61. A gap that wide usually means heavy scripts and images that hit phones hardest.

6 KiB could be saved by minifying CSS.

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

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

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

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

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

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

16 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-17, real Chrome visitors' tap response (inp) went from 88 ms to 105 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 3.2 MB in 37 requests on a phone: images 2.2 MB (20), fonts 847 KiB (8) and scripts 105 KiB (6). Under 2 MB keeps phones on slow connections fast.

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

6 images (579 KiB) 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.

1 image is downloaded at several times the size a phone draws it, for example 609d9413e6ba193fe4833a0c_Request a new asset.svg at 840 px wide, shown at 274 px. Resized copies would save about 2 KiB.

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

<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

All page content should be contained by landmarks: 19 elements on the page fail this check, rated moderate by axe-core.

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

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

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

Headings should not be empty: 5 elements on the page fail this check, rated minor by axe-core.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 3 <h1> headlines (“Custody to Client. Delivered.”, “Selective by design” and “Board-level value”). One clear main headline is easier for people and search engines.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

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

No XML sitemap at https://www.platform1online.com/sitemap.xml, so Google discovers your pages only by following links.

The homepage links to 25 pages on platform1online.com and 6 external pages.

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.

There is no https://www.platform1online.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.platform1online.com/disclosures is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/, https://www.platform1online.com/disclosures, https://www.platform1online.com/product, https://www.platform1online.com/company, https://www.platform1online.com/contact and https://www.platform1online.com/news and 1 other all use the title “Platform One - the intuitive investment platform”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.platform1online.com/team/joachim-miller has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.platform1online.com/disclosures, https://www.platform1online.com/product, https://www.platform1online.com/company, https://www.platform1online.com/contact, https://www.platform1online.com/news and https://www.platform1online.com/consumer-duty use the same meta description. A description written for each page earns more clicks.

https://www.platform1online.com/team/joachim-miller 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 12 pages linked from your homepage and read each the way a search engine does.

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

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

Social proof on the homepage: 10 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

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

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

The homepage carries about 1,064 words of visible text.

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