pl-devsite.com website review

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

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

14 images could be 2.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

8 third-party services load with your homepage (tailwindcss.com, Wistia and prettylitter.com and others), adding 1.3 MB and 1.5 s of main-thread time.

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

tailwindcss.com costs a phone 628 ms of main-thread work and 124 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.

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

Wistia costs a phone 401 ms of main-thread work and 338 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.

prettylitter.com costs a phone 225 ms of main-thread work and 308 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,504 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

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

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

Polyfills for old browsers add 27 KiB JavaScript that modern phones do not need.

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

13 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.

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

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

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

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

23 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.

Your homepage downloads 10.9 MB in 239 requests on a phone: images 4.9 MB (67), media 3.8 MB (1) and scripts 1.3 MB (66). Under 2 MB keeps phones on slow connections fast.

3 images weigh 2.1 MB together. On a phone connection a single image that size takes seconds.

29 images (4.7 MB) 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 trusted_USA_today.png at 2,081 px wide, shown at 96 px. Resized copies would save about 113 KiB.

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

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

28 elements have a tabindex above 0, which scrambles the keyboard order.

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

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

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

The robots meta tag says “noindex, nofollow”: Google is told not to list this page at all.

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

Google's crawler is blocked from indexing this page.

Your title is only 9 characters: “prettydev”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

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

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

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

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

The homepage links to 26 pages on pl-devsite.com and 50 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.

https://pl-devsite.com/pages/reviews and https://pl-devsite.com/pages/faq are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://pl-devsite.com/pages/faq and https://pl-devsite.com/pages/get-started have no meta description, so Google writes the search snippet from whatever text it finds.

We fetched 4 pages linked from your homepage and read each the way a search engine does.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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

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.

There is no form on the homepage, so every lead has to click through to another page first.

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

Before a visitor clicks anything, the page loads Klaviyo (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 8 cookies, 1 of them by other companies (measured from a US location before any click).

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