Website review, no card needed
nickiminajqueen.com website review
Visit site (opens in a new tab)Reviewed 9 November 202631 issues · 78 checks
This review found 31 issues worth fixing on nickiminajqueen.com, 8 of them high impact, across 78 checks. The most urgent: fails Core Web Vitals for real visitors. 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
80B- #48,294 of 123,940 reviewed websitesbeats 55%
- #31,922 of 69,726 online storesbeats 48%
- #30,676 of 63,429 Shopify storesbeats 45%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.7 s |
| May 30, 2026 | 1.6 s |
| Jun 6, 2026 | 1.5 s |
| Jun 13, 2026 | 1.5 s |
| Jun 20, 2026 | 1.4 s |
| Jun 27, 2026 | 1.4 s |
| Jul 4, 2026 | 1.4 s |
| Jul 11, 2026 | 1.4 s |
| Jul 18, 2026 | 1.5 s |
| Jul 25, 2026 | 1.5 s |
| Aug 1, 2026 | 1.6 s |
| Aug 8, 2026 | 1.6 s |
| Aug 15, 2026 | 1.5 s |
| Aug 22, 2026 | 1.6 s |
| Aug 29, 2026 | 1.4 s |
| Sep 5, 2026 | 1.4 s |
| Sep 12, 2026 | 1.5 s |
| Sep 19, 2026 | 1.4 s |
| Sep 26, 2026 | 1.4 s |
| Oct 3, 2026 | 1.4 s |
| Oct 10, 2026 | 1.7 s |
| Oct 17, 2026 | 1.7 s |
| Oct 24, 2026 | 1.6 s |
| Oct 31, 2026 | 1.6 s |
| Nov 7, 2026 | 1.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 319 ms |
| May 30, 2026 | 313 ms |
| Jun 6, 2026 | 330 ms |
| Jun 13, 2026 | 328 ms |
| Jun 20, 2026 | 306 ms |
| Jun 27, 2026 | 296 ms |
| Jul 4, 2026 | 266 ms |
| Jul 11, 2026 | 236 ms |
| Jul 18, 2026 | 241 ms |
| Jul 25, 2026 | 241 ms |
| Aug 1, 2026 | 239 ms |
| Aug 8, 2026 | 244 ms |
| Aug 15, 2026 | 244 ms |
| Aug 22, 2026 | 289 ms |
| Aug 29, 2026 | 311 ms |
| Sep 5, 2026 | 331 ms |
| Sep 12, 2026 | 347 ms |
| Sep 19, 2026 | 302 ms |
| Sep 26, 2026 | 302 ms |
| Oct 3, 2026 | 288 ms |
| Oct 10, 2026 | 391 ms |
| Oct 17, 2026 | 412 ms |
| Oct 24, 2026 | 408 ms |
| Oct 31, 2026 | 404 ms |
| Nov 7, 2026 | 292 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.5 s
1.1 s
1.6 s
2.1 s
2.7 s
3.2 s
3.7 s
4.2 s
Speed
Main-thread work: 6.9 s
A phone's processor spends 6.9 s on main-thread work while loading, 2.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Improve image delivery
1.3 MB35 images could be 1.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, sdiapi.com and transcend-cdn.com and others), adding 1.2 MB and 1.2 s of main-thread time.
Mobile performance score: 69
69/100Your mobile performance score is 69. Pages that score under 90 lose visitors before the first paint.
Use efficient cache lifetimes
500 ms · 244 KiB9 files are served with short cache lifetimes, so returning visitors download them again (244 KiB).
Google Tag Manager adds 666 ms
666 msGoogle Tag Manager costs a phone 666 ms of main-thread work and 343 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.
Render-blocking requests
650 ms5 files block the first paint until they finish downloading. Deferring or inlining them could save about 650 ms.
12 long tasks on the main thread
12 long tasks block the main thread while loading, the longest for 561 ms. During a long task the page ignores taps.
Reduce unused JavaScript
303 KiBAbout 303 KiB of JavaScript is downloaded but never used on this page.
sdiapi.com adds 263 ms
263 mssdiapi.com costs a phone 263 ms of main-thread work and 92 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.
1,830 HTML elements
The page has 1,830 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Shopify adds 46 ms
46 msShopify costs a phone 46 ms of main-thread work and 564 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.
Reduce unused CSS
13 KiBAbout 13 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
8 KiBPolyfills for old browsers add 8 KiB JavaScript that modern phones do not need.
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: 8 ms
8 msYour server sent the HTML in 8 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.
Time to Interactive: 12.4 s
12.4 sThe page becomes fully interactive after 12.4 s. Good is under 3.8 s.
Total Blocking Time: 854 ms
854 msScripts block taps and scrolling for 854 ms in total while the page loads. Good is under 200 ms.
Real-user INP: 314 ms
314 msReal visitors wait 314 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Largest Contentful Paint: 3.6 s
3.6 sYour largest element takes 3.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “BANNED FROM NO TEE FRONT”.
Speed Index: 3.5 s
3.5 sVisually, the page fills in at 3.5 s (Speed Index). Good is under 3.4 s.
Tap response (INP) got 10% slower for real visitors
+10%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 319 ms to 292 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 checks passed
Real-user LCP: 1.6 s
1.6 sReal visitors wait 1.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.5 s
1.5 sReal visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 499 ms
499 msReal visitors wait 499 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 10% faster for real visitors
-10%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.7 s to 1.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 4.6 MB in 232 requests
4.6 MBYour homepage downloads 4.6 MB in 232 requests on a phone: images 2.6 MB (40), scripts 1,004 KiB (57) and other files 961 KiB (126). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
NM---_0001_PRODUCT_NMIN_25_ECOMM_CG_IAMTHEMAINHER_1.png 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 1.3 g of CO₂ per visit
1.32 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.32 g of CO₂e: 157.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
7 images without alt text
7 images have no alt text, which hurts accessibility and image search.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
2 links without text
2 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h1 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
43 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 3 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
2 H1 headlines
There are 2 <h1> headlines (“NICKI MINAJ” and “NICKI MINAJ”). One clear main headline is easier for people and search engines.
149 internal links, 19 external
The homepage links to 149 pages on nickiminajqueen.com and 19 external pages.
6 checks passed
Meta description: 98 characters
Your meta description is 98 characters: “Shop exclusive music and merch from the Official Nicki Minaj Store. Vinyl, hoodies, CDs, and more.”.
Title: 31 characters
Your title is a healthy 31 characters: “NICKI MINAJ STORE - NICKI MINAJ”.
Canonical URL set
The canonical URL is https://shop.nickiminajofficial.com/.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
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://shop.nickiminajofficial.com/sitemap.xml.
AI search readiness
No Organization structured data
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.
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 (436 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://shop.nickiminajofficial.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
12 pages share a meta description
https://shop.nickiminajofficial.com/collections/gag-city-resort, https://shop.nickiminajofficial.com/collections/pinkprint-10-year-anniversary, https://shop.nickiminajofficial.com/collections/pink-friday-2-all, https://shop.nickiminajofficial.com/collections/pink-friday-2-world-tour-1, https://shop.nickiminajofficial.com/collections/pink-friday-tour-leg-2 and https://shop.nickiminajofficial.com/collections/summer-2024 and 6 others use the same meta description. A description written for each page earns more clicks.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 70 found) and read each the way a search engine does.
7 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 15 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Uncaught TypeError: Cannot assign to read only property 'open' of object '#<Window>'”.
2 checks passed
Tap targets are thumb-sized
63 of 77 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
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 307 words of copy
The homepage carries about 307 words of visible text.
3 checks passed
7 calls to action
The homepage has 7 calls to action, for example “Smoke Shop”, “Record Shop” and “Shop All”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Meta Pixel and 2 mores (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.
22 cookies set on arrival
22Opening the homepage sets 22 cookies, 1 of them by other companies (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.
38 other companies contacted
Loading the homepage contacts 38 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 nickiminajqueen.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
Your storefront loads 3 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
trackedlink.net · printful.com · esc-apps-cdn.com
Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info
Upkeep, stack and company
Stack
- E-commerce
- Shopify
- Analytics
- Google Tag Manager
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 31 issues on nickiminajqueen.com, including 18 speed issues, 2 SEO issues and 2 conversion gaps. 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.