peekaboo.ug website review

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Shopify and omnisnippet1.com and others), adding 6.8 MB and 929 ms of main-thread time.

Shopify costs a phone 389 ms of main-thread work and 6.3 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.

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

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

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

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

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

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

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

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

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.

5 KiB could be saved by minifying JavaScript.

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 68.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “6 (1).jpg__PID:ae2476c4-c164-40a5-a46b-c364f1523097”.

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

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

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

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

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

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 105 ms to 96 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 28.4 MB in 538 requests on a phone: images 26.2 MB (271), other files 1.0 MB (184) and scripts 931 KiB (69). Under 2 MB keeps phones on slow connections fast.

8 images are downloaded at several times the size a phone draws them, for example optim-Fashion.png at 462 px wide, shown at 103 px. Resized copies would save about 1.6 MB.

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

2 images (410 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.

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

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

Scrollable region must have keyboard access: 4 elements on the page fail this check, rated serious by axe-core.

Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one banner landmark: 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.

1 frame has no title, so screen-reader users cannot tell what it contains.

Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

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

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

There are 2 <h1> headlines (“” and “Peekaboo – #1 Baby & Mother Shop in Kenya”). One clear main headline is easier for people and search engines.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

The homepage links to 243 pages on peekaboo.ug and 9 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://www.peekaboo.ug/collections/fashion, https://www.peekaboo.ug/collections/shirts/Tops+T-shirts+Shirts and https://www.peekaboo.ug/collections/toys have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 12 pages by a URL that isn't their canonical one, for example https://www.peekaboo.ug/collections/sets-suits/Sets+Suits, whose canonical is https://www.peekaboo.ug/collections/sets-suits. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.peekaboo.ug/collections/shorts-skirts-jeans/Shorts+Skirts+Jeans+Pants, https://www.peekaboo.ug/collections/toy-guns-weapons/Toy-Guns+Weapons and https://www.peekaboo.ug/collections/art-craft-hobby-kits/Art-Craft+Hobby-Kits took over 3 s to send their HTML from our server.

We fetched 15 pages linked from your homepage (of 102 found) and read each the way a search engine does.

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

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.

Your homepage shows a map 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.

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.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (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 15 cookies, 1 of them by other companies (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 21 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.