wearepop.com website review

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

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

About 221 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 930 ms faster on a phone.

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

5 third-party services load with your homepage (Google Tag Manager, Google Analytics and Google Fonts and others), adding 6.0 MB and 193 ms of main-thread time.

azurefd.net costs a phone 0 ms of main-thread work and 5.6 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.

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

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

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

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 5.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “WHO WE ARE We challenge the digital status quo to enrich co…”.

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

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

4 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 6.7 MB in 38 requests on a phone: media 5.6 MB (1), images 567 KiB (7) and scripts 446 KiB (11). Under 2 MB keeps phones on slow connections fast.

4 images are downloaded at several times the size a phone draws them, for example sm_img_casestudy_pepsico_home_Tile_818af2a5cc.webp at 1,440 px wide, shown at 350 px. Resized copies would save about 166 KiB.

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

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

SVG elements with an img role do not have an accessible text alternative (4 elements).

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

Your title is only 20 characters: “POP | Digital Agency”. 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 canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

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

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 16 pages on wearepop.com and 2 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.wearepop.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.wearepop.com/work, https://www.wearepop.com/about and https://www.wearepop.com/careers have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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.

The homepage has only about 143 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.

Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

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