persebayastore.com website review

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

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

15 images could be 1.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 900 ms faster on a phone.

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

Your mobile performance score is 63 (desktop: 69). Pages that score under 90 lose visitors before the first paint.

About 35 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

33 KiB could be saved by minifying JavaScript.

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

bonloyalty.com costs a phone 59 ms of main-thread work and 357 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.

8 third-party services load with your homepage (jQuery CDN, Google Tag Manager and bonloyalty.com and others), adding 769 KiB and 448 ms of main-thread time.

2 long tasks block the main thread while loading, the longest for 125 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.

3 KiB could be saved by minifying CSS.

1 file is served with short cache lifetimes, so returning visitors download them again (1 KiB).

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

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

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

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

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

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

Real visitors wait 901 ms for your server to start answering (75th percentile). Good is under 800 ms.

35 images have no width and height attributes, so the layout jumps as each one loads.

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

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

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

Your homepage downloads 4.5 MB in 253 requests on a phone: images 2.3 MB (27), other files 1.1 MB (170) and scripts 940 KiB (43). Under 2 MB keeps phones on slow connections fast.

4 images are downloaded at several times the size a phone draws them, for example KIDS-COLLECTION_1000x1000_3aa5c753-4a81-4f96-92a8-7816153ee1 at 1,417 px wide, shown at 390 px. Resized copies would save about 247 KiB.

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

1 image (71 KiB) is 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 1.27 g of CO₂e: 152.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 element use ARIA attributes their role does not allow, which confuses screen readers.

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

Certain ARIA roles must be contained by particular parents: 1 element on the page fails this check, rated critical by axe-core.

ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

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

1 element hidden from screen readers can still receive keyboard focus.

ARIA toggle fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

13 images have no alt text, which hurts accessibility and image search.

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

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

Elements marked as presentational should be consistently ignored: 1 element on the page fails this check, rated minor by axe-core.

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

The homepage links to 220 pages on persebayastore.com and 0 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.persebayastore.com/collections/all, https://www.persebayastore.com/collections/polo-kemeja, https://www.persebayastore.com/collections/pakaian-wanita, https://www.persebayastore.com/collections/accessories, https://www.persebayastore.com/collections/tas-dompet and https://www.persebayastore.com/collections/topi and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

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

4 images failed to load on a phone, for example https://www.persebayastore.com/.

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.

Your homepage shows a street address 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 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 shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

Before a visitor clicks anything, the page loads 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 5 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 13 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.