preply.com website review

About 708 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.1 s faster on a phone.

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

A phone's processor spends 5.7 s on main-thread work while loading, 3.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

8 third-party services load with your homepage (Facebook, Hubspot and TikTok and others), adding 816 KiB and 803 ms of main-thread time.

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

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

Facebook costs a phone 262 ms of main-thread work and 264 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.

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

About 20 KiB of CSS is downloaded but never applied on this page.

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

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.

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

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

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

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

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

Real visitors wait 270 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

Real visitors see the first content after 2.0 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.

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

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

Your homepage downloads 3.1 MB in 200 requests on a phone: scripts 2.5 MB (81), images 297 KiB (29) and HTML 206 KiB (4). Under 2 MB keeps phones on slow connections fast.

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

Delayed refresh under 20 hours must not be used: 1 element on the page fails this check, rated critical by axe-core.

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

Your page has no <title>, so Google has to invent the blue link in search results.

No meta description, so Google writes its own snippet from whatever text it finds.

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

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

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

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

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

There is no robots.txt at preply.com/robots.txt, the first file search crawlers ask for.

The homepage links to only 1 page on your own site, so visitors and crawlers find few routes into the rest of it.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

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

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.

13 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

Large scripts ship without source maps.

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

Your homepage answered with HTTP 403, so visitors and search engines may see an error page.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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 has only about 2 words of visible text; thin pages give Google and first-time buyers little to go on.

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.

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