myfonts.com website review

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

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

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

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

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

8 third-party services load with your homepage (monotype.com, Intercom and Google Tag Manager and others), adding 2.3 MB and 2.0 s of main-thread time.

10 files block the first paint until they finish downloading. Deferring or inlining them could save about 800 ms.

monotype.com costs a phone 342 ms of main-thread work and 930 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.

Intercom costs a phone 311 ms of main-thread work and 236 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.

Google Tag Manager costs a phone 278 ms of main-thread work and 533 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.

Privy costs a phone 228 ms of main-thread work and 411 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.

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

UpSellit costs a phone 254 ms of main-thread work and 78 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.

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

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

20 KiB could be saved by minifying JavaScript.

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 22.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Montreux Grotesk”.

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

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

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

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

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

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

For real visitors the layout shifts by 0.17 (75th percentile). Good is under 0.1.

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

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

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

Your homepage downloads 6.6 MB in 532 requests on a phone: scripts 2.6 MB (106), other files 2.6 MB (304) and fonts 766 KiB (21). Under 2 MB keeps phones on slow connections fast.

9FFKVklXOfhwVdg5HuIZ2Uep_4478684c2cd4956ddf9bddb079eb5cb6.pn 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).

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

12 elements use ARIA attributes their role does not allow, which confuses screen readers.

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

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

Elements must only use permitted ARIA attributes: 2 elements on the page fail this check, rated serious by axe-core.

Interactive controls must not be nested: 2 elements on the page fail this check, rated serious by axe-core.

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

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

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

Elements marked as presentational should be consistently ignored: 4 elements on the page fail this check, rated minor by axe-core.

Elements with visible text labels do not have matching accessible names. (1 element).

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

Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: url points at a different host (https://www.monotype.com/)”.

6 links have no real href, so search engines can't follow them.

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

The homepage links to 44 pages on myfonts.com and 6 external pages.

The HTML your server sends has 195 of the 356 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

https://www.myfonts.com/collections/novel-sans-rounded-font-atlasfontfoundry has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.myfonts.com/collections/montreux-grotesk-font-rohh, https://www.myfonts.com/collections/rohh-foundry, https://www.myfonts.com/collections/calenza-font-mostardesign, https://www.myfonts.com/collections/mostardesign-foundry, https://www.myfonts.com/collections/novel-sans-rounded-font-atlasfontfoundry and https://www.myfonts.com/collections/atlasfontfoundry-foundry and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.myfonts.com/collections/montreux-grotesk-font-rohh, https://www.myfonts.com/collections/calenza-font-mostardesign, https://www.myfonts.com/collections/novel-sans-rounded-font-atlasfontfoundry, https://www.myfonts.com/collections/atlasfontfoundry-foundry, https://www.myfonts.com/collections/denz-font-paratype and https://www.myfonts.com/collections/raimundo-font-latinotype and 1 other have 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 15 pages linked from your homepage (of 18 found) and read each the way a search engine does.

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

2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

5 errors were logged to the browser console while the page loaded, for example “loadViewPortSpecificCSS is not defined”.

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

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

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.

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

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

Before a visitor clicks anything, the page loads Google Ads and Google Tag Manager (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

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

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