Website review, no card needed
mariab.pk website review
Visit site (opens in a new tab)Reviewed 17 November 202642 issues · 75 checks
This review found 42 issues worth fixing on mariab.pk, 22 of them high impact, across 75 checks. The most urgent: improve image delivery. 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
65D- #106,979 of 115,138 reviewed websitesbeats 6%
- #64,066 of 66,397 online storesbeats 3%
- #58,964 of 60,723 Shopify storesbeats 2%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 2.8 s |
| Jun 6, 2026 | 2.8 s |
| Jun 13, 2026 | 2.8 s |
| Jun 20, 2026 | 2.8 s |
| Jun 27, 2026 | 2.8 s |
| Jul 4, 2026 | 2.9 s |
| Jul 11, 2026 | 3.0 s |
| Jul 18, 2026 | 3.1 s |
| Jul 25, 2026 | 3.2 s |
| Aug 1, 2026 | 3.2 s |
| Aug 8, 2026 | 3.1 s |
| Aug 15, 2026 | 3.1 s |
| Aug 22, 2026 | 3.1 s |
| Aug 29, 2026 | 3.0 s |
| Sep 5, 2026 | 3.0 s |
| Sep 12, 2026 | 3.2 s |
| Sep 19, 2026 | 3.5 s |
| Sep 26, 2026 | 3.9 s |
| Oct 3, 2026 | 4.2 s |
| Oct 10, 2026 | 4.4 s |
| Oct 17, 2026 | 4.5 s |
| Oct 24, 2026 | 4.6 s |
| Oct 31, 2026 | 4.7 s |
| Nov 7, 2026 | 4.7 s |
| Nov 14, 2026 | 4.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 256 ms |
| Jun 6, 2026 | 264 ms |
| Jun 13, 2026 | 270 ms |
| Jun 20, 2026 | 272 ms |
| Jun 27, 2026 | 271 ms |
| Jul 4, 2026 | 270 ms |
| Jul 11, 2026 | 271 ms |
| Jul 18, 2026 | 271 ms |
| Jul 25, 2026 | 272 ms |
| Aug 1, 2026 | 277 ms |
| Aug 8, 2026 | 289 ms |
| Aug 15, 2026 | 296 ms |
| Aug 22, 2026 | 303 ms |
| Aug 29, 2026 | 304 ms |
| Sep 5, 2026 | 304 ms |
| Sep 12, 2026 | 307 ms |
| Sep 19, 2026 | 317 ms |
| Sep 26, 2026 | 334 ms |
| Oct 3, 2026 | 348 ms |
| Oct 10, 2026 | 356 ms |
| Oct 17, 2026 | 360 ms |
| Oct 24, 2026 | 365 ms |
| Oct 31, 2026 | 367 ms |
| Nov 7, 2026 | 367 ms |
| Nov 14, 2026 | 350 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
Speed
Improve image delivery
1.9 s · 774 KiB19 images could be 774 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.9 s faster on a phone.
Render-blocking requests
1.4 s19 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.
Mobile performance score: 41
41/100Your mobile performance score is 41. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
6,841 HTML elements
The page has 6,841 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Main-thread work: 4.3 s
A phone's processor spends 4.3 s on main-thread work while loading, 1.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
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.2 MB and 810 ms of main-thread time.
Reduce unused JavaScript
300 ms · 531 KiBAbout 531 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.
Google Tag Manager adds 403 ms
403 msGoogle Tag Manager costs a phone 403 ms of main-thread work and 532 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.
12 long tasks on the main thread
12 long tasks block the main thread while loading, the longest for 393 ms. During a long task the page ignores taps.
Legacy JavaScript
150 ms · 7 KiBPolyfills for old browsers add 7 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
97 KiB22 files are served with short cache lifetimes, so returning visitors download them again (97 KiB).
Reduce unused CSS
22 KiBAbout 22 KiB of CSS is downloaded but never applied on this page.
Duplicated JavaScript
6 KiB6 KiB JavaScript is shipped twice across bundles.
Minify JavaScript
6 KiB6 KiB could be saved by minifying JavaScript.
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: 183 ms
183 msYour server sent the HTML in 183 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 LCP: 5.0 s
5.0 sReal visitors wait 5.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 4.4 s
4.4 sReal visitors see the first content after 4.4 s (75th percentile). Good is under 1.8 s.
First Contentful Paint: 8.7 s
8.7 sThe first text or image appears after 8.7 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 21.8 s
21.8 sYour largest element takes 21.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 26.4 s
26.4 sThe page becomes fully interactive after 26.4 s. Good is under 3.8 s.
Speed Index: 8.7 s
8.7 sVisually, the page fills in at 8.7 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 627 ms
627 msScripts block taps and scrolling for 627 ms in total while the page loads. Good is under 200 ms.
Real-user INP: 428 ms
428 msReal visitors wait 428 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 38% slower for real visitors
+38%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 256 ms to 350 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 66% slower for real visitors
+66%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 2.8 s to 4.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Real-user TTFB: 610 ms
610 msReal visitors wait 610 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 7.1 MB in 276 requests
7.1 MBYour homepage downloads 7.1 MB in 276 requests on a phone: images 3.5 MB (40), scripts 1.4 MB (82) and HTML 1.4 MB (3). Under 2 MB keeps phones on slow connections fast.
5 images below the first screen load straight away
5 images further down the page (432 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
2 images far larger than shown
84 KiB2 images are downloaded at several times the size a phone draws them, for example Jewelry_830X1166_f7aa6fc1-4a3a-414b-b91b-797880ae2ca0_720x.j at 720 px wide, shown at 171 px. Resized copies would save about 84 KiB.
5 images in older formats
5 images (454 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.
About 2.0 g of CO₂ per visit
2.01 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.01 g of CO₂e: 241.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Images must have alternative text (74 elements)
Images must have alternative text: 74 elements on the page fail this check, rated critical by axe-core.
14 text elements with low contrast
14 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
8 tap targets too small
8 tap targets are too small or too close together to hit reliably with a finger.
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
34 links without text
34 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
1 checks passed
49 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Only 0 internal links
The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.
6 checks passed
Meta description: 149 characters
Your meta description is 149 characters: “Shop the latest fashion at Maria. B collection online from traditional to modern, we have it all. Discover the perfect …”.
Title: 50 characters
Your title is a healthy 50 characters: “Maria.B. Collection Online – Maria.B. Designs (PK)”.
Canonical URL set
The canonical URL is https://www.mariab.pk/.
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://www.mariab.pk/sitemap.xml.
AI search readiness
Most text only appears after JavaScript runs
0%A phone browser shows 967 words, but the HTML your server sends has only 0. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.
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.
2 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.
llms.txt published
The site publishes https://www.mariab.pk/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Best practices
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to fetch”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
38 of 44 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 calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 967 words of copy
The homepage carries about 967 words of visible text.
1 checks passed
Analytics in place
Analytics detected: Microsoft Clarity.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Meta Pixel and 1 more (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.
18 cookies set on arrival
18Opening the homepage sets 18 cookies, 13 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.
22 other companies contacted
Loading the homepage contacts 22 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 mariab.pk, 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 6 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Geoip Country Redirect · Judge Me Reviews · Mp Size Chart · chimpstatic.com · pdfflipbook.com · bestfreecdn.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
- Microsoft Clarity
- Hosting
- Cloudflare
Company
- Headquarters
- Raiwind
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 42 issues on mariab.pk, including 20 speed issues, 3 SEO issues and 4 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.