Website review, no card needed
mypartycentre.com website review
Visit site (opens in a new tab)Reviewed 20 October 202647 issues · 85 checks
This review found 47 issues worth fixing on mypartycentre.com, 17 of them high impact, across 85 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
63D- #117,642 of 123,879 reviewed websitesbeats 4%
- #68,150 of 69,698 online storesbeats 2%
- #62,281 of 63,406 Shopify storesbeats 1%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.4 s |
| May 9, 2026 | 2.3 s |
| May 16, 2026 | 2.3 s |
| May 23, 2026 | 2.3 s |
| May 30, 2026 | 2.3 s |
| Jun 6, 2026 | 2.3 s |
| Jun 13, 2026 | 2.3 s |
| Jun 20, 2026 | 2.3 s |
| Jun 27, 2026 | 2.4 s |
| Jul 4, 2026 | 2.3 s |
| Jul 11, 2026 | 2.2 s |
| Jul 18, 2026 | 2.2 s |
| Jul 25, 2026 | 2.2 s |
| Aug 1, 2026 | 2.3 s |
| Aug 8, 2026 | 2.4 s |
| Aug 15, 2026 | 2.3 s |
| Aug 22, 2026 | 2.3 s |
| Aug 29, 2026 | 2.2 s |
| Sep 5, 2026 | 2.1 s |
| Sep 12, 2026 | 2.2 s |
| Sep 19, 2026 | 2.2 s |
| Sep 26, 2026 | 2.2 s |
| Oct 3, 2026 | 2.3 s |
| Oct 10, 2026 | 2.3 s |
| Oct 17, 2026 | 2.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 163 ms |
| May 9, 2026 | 174 ms |
| May 16, 2026 | 178 ms |
| May 23, 2026 | 185 ms |
| May 30, 2026 | 181 ms |
| Jun 6, 2026 | 168 ms |
| Jun 13, 2026 | 169 ms |
| Jun 20, 2026 | 172 ms |
| Jun 27, 2026 | 180 ms |
| Jul 4, 2026 | 187 ms |
| Jul 11, 2026 | 183 ms |
| Jul 18, 2026 | 189 ms |
| Jul 25, 2026 | 189 ms |
| Aug 1, 2026 | 193 ms |
| Aug 8, 2026 | 203 ms |
| Aug 15, 2026 | 190 ms |
| Aug 22, 2026 | 190 ms |
| Aug 29, 2026 | 185 ms |
| Sep 5, 2026 | 173 ms |
| Sep 12, 2026 | 180 ms |
| Sep 19, 2026 | 185 ms |
| Sep 26, 2026 | 187 ms |
| Oct 3, 2026 | 210 ms |
| Oct 10, 2026 | 218 ms |
| Oct 17, 2026 | 216 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
0.8 s
1.6 s
2.3 s
3.1 s
3.9 s
4.7 s
5.5 s
6.3 s
Speed
Reduce unused JavaScript
2.4 s · 476 KiBAbout 476 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.4 s faster on a phone.
Render-blocking requests
2.3 s17 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.3 s.
Mobile performance score: 25
25/100Your mobile performance score is 25 (desktop: 42). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
5,284 HTML elements
The page has 5,284 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
150 ms · 5.7 MB56 images could be 5.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
Reduce unused CSS
900 ms · 80 KiBAbout 80 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 900 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Shopify and Clarity and others), adding 1.5 MB and 753 ms of main-thread time.
Google Tag Manager adds 524 ms
524 msGoogle Tag Manager costs a phone 524 ms of main-thread work and 721 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.
Main-thread work: 4.0 s
A phone's processor spends 4.0 s on main-thread work while loading, 1.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
10 long tasks on the main thread
10 long tasks block the main thread while loading, the longest for 250 ms. During a long task the page ignores taps.
Shopify adds 136 ms
136 msShopify costs a phone 136 ms of main-thread work and 595 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.
Legacy JavaScript
150 ms · 30 KiBPolyfills for old browsers add 30 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Use efficient cache lifetimes
26 KiB5 files are served with short cache lifetimes, so returning visitors download them again (26 KiB).
Minify CSS
12 KiB12 KiB could be saved by minifying CSS.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 9 ms
9 msYour server sent the HTML in 9 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
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.
Real-user CLS: 0.43
0.43For real visitors the layout shifts by 0.43 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 32.0 s
32.0 sYour largest element takes 32.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “mobile offer image”.
Time to Interactive: 33.7 s
33.7 sThe page becomes fully interactive after 33.7 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.86
0.86The layout shifts by 0.86 while loading, so content jumps under the reader's thumb. Good is under 0.1.
First Contentful Paint: 5.8 s
5.8 sThe first text or image appears after 5.8 s on a phone. Good is under 1.8 s.
Speed Index: 9.0 s
9.0 sVisually, the page fills in at 9.0 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 3.3 s
3.3 sReal visitors wait 3.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 332 ms
332 msReal visitors wait 332 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 29% slower for real visitors
+29%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 163 ms to 216 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.1 s
2.1 sReal visitors see the first content after 2.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 858 ms
858 msReal visitors wait 858 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 340 ms
340 msScripts block taps and scrolling for 340 ms in total while the page loads. Good is under 200 ms.
19 images without width and height
19 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
-1%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).
Images and page weight
Page weight: 10.2 MB in 258 requests
10.2 MBYour homepage downloads 10.2 MB in 258 requests on a phone: images 7.8 MB (79), scripts 1.4 MB (109) and other files 576 KiB (44). Under 2 MB keeps phones on slow connections fast.
5 images over 500 KB
5 images weigh 4.1 MB together. On a phone connection a single image that size takes seconds.
7 images far larger than shown
774 KiB7 images are downloaded at several times the size a phone draws them, for example halloween_balloons_1_4_cdb06f0a-6b0c-4bb1-8dea-3eba968a4c13. at 1,254 px wide, shown at 170 px. Resized copies would save about 774 KiB.
11 images in older formats
11 images (4.8 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.
An image on the first screen is lazy-loaded
Pop_up_Mobile_Image.jpg 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).
About 2.9 g of CO₂ per visit
2.88 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.88 g of CO₂e: 345.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
19 text elements with low contrast
19 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
108 form fields without a label
108 form fields have no label, so screen readers announce an empty box and autofill guesses.
All page content should be contained by landmarks (5 elements)
All page content should be contained by landmarks: 5 elements on the page fail this check, rated moderate by axe-core.
5 links without text
5 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h2 → h4, h1 → h3 and h2 → h4), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (6 elements).
2 checks passed
Every image has alt text
All 146 images in the HTML carry an alt attribute.
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 4 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
2 H1 headlines
There are 2 <h1> headlines (“” and “”). One clear main headline is easier for people and search engines.
Structured data has 3 problems
Structured data found (BreadcrumbList, ItemList, Organization and WebSite) but with 3 problems, for example “WebSite: missing name”.
8 links with vague text
8 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
Open Graph partly set
Open Graph is missing og:title and og:description, so shared links fall back to guesses.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
643 internal links, 8 external
The homepage links to 643 pages on mypartycentre.com and 8 external pages.
5 checks passed
Meta description: 156 characters
Your meta description is 156 characters: “Party Centre is one of the largest online superstores for party supplies in UAE. We are one-stop solution for all kinds…”.
Title: 52 characters
Your title is a healthy 52 characters: “Party Centre - The Online Party Superstore Dubai UAE”.
Canonical URL set
The canonical URL is https://mypartycentre.com/.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://mypartycentre.com/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing name, description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
3 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (2,396 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://mypartycentre.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://mypartycentre.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://mypartycentre.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
2 pages share a title
https://mypartycentre.com/collections/catalogues and https://mypartycentre.com/collections/catalogue all use the title “CATALOGS”. Search engines can't tell which page to show for a search, so each competes with the others.
4 pages without a meta description
https://mypartycentre.com/collections/catalogues, https://mypartycentre.com/customer_authentication/redirect, https://mypartycentre.com/pages/wishlist and https://mypartycentre.com/collections/catalogue have no meta description, so Google writes the search snippet from whatever text it finds.
4 links to non-canonical URLs
Your homepage links to 4 pages by a URL that isn't their canonical one, for example https://mypartycentre.com/collections/catalogues, whose canonical is https://mypartycentre.com/collections/catalogs. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
1 page without an H1
https://mypartycentre.com/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 196 found) and read each the way a search engine does.
1 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Best practices
10 broken images
10 images failed to load on a phone, for example https://mypartycentre.com/.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “FM not loaded yet ReferenceError: FM is not defined”.
2 checks passed
Tap targets are thumb-sized
57 of 70 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 1,141 words of copy
The homepage carries about 1,141 words of visible text.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Learn more about this section”.
64 calls to action
The homepage has 64 calls to action, for example “Signup”, “Shop All »” and “Shop Now”.
38 short forms
38 short forms (3 fields at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 26 testimonial or review blocks and 2 trust badges.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 3 phone links and 1 email link.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity (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.
12 cookies set on arrival
12Opening the homepage sets 12 cookies (measured from a US location before any click).
No consent tool detected
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.
27 other companies contacted
Loading the homepage contacts 27 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at mypartycentre.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- jQuery
- E-commerce
- Shopify
- Analytics
- Google Analytics | Google Tag Manager | Microsoft Clarity
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 47 issues on mypartycentre.com, including 25 speed issues and 3 SEO issues. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.