Website review, no card needed
macduggal.com website review
Visit site (opens in a new tab)Reviewed 19 November 202643 issues · 93 checks
This review found 43 issues worth fixing on macduggal.com, 15 of them high impact, across 93 checks. The most urgent: main-thread work: 13.2 s. 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
76C- #73,232 of 120,154 reviewed websitesbeats 34%
- #47,160 of 68,064 online storesbeats 26%
- #44,727 of 62,030 Shopify storesbeats 23%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 1.4 s |
| Jun 6, 2026 | 1.4 s |
| Jun 13, 2026 | 1.4 s |
| Jun 20, 2026 | 1.4 s |
| Jun 27, 2026 | 1.5 s |
| Jul 4, 2026 | 1.5 s |
| Jul 11, 2026 | 1.4 s |
| Jul 18, 2026 | 1.4 s |
| Jul 25, 2026 | 1.4 s |
| Aug 1, 2026 | 1.5 s |
| Aug 8, 2026 | 1.5 s |
| Aug 15, 2026 | 1.5 s |
| Aug 22, 2026 | 1.5 s |
| Aug 29, 2026 | 1.6 s |
| Sep 5, 2026 | 1.6 s |
| Sep 12, 2026 | 1.6 s |
| Sep 19, 2026 | 1.6 s |
| Sep 26, 2026 | 1.6 s |
| Oct 3, 2026 | 1.7 s |
| Oct 10, 2026 | 1.7 s |
| Oct 17, 2026 | 1.7 s |
| Oct 24, 2026 | 1.7 s |
| Oct 31, 2026 | 1.7 s |
| Nov 7, 2026 | 1.8 s |
| Nov 14, 2026 | 1.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 161 ms |
| Jun 6, 2026 | 162 ms |
| Jun 13, 2026 | 164 ms |
| Jun 20, 2026 | 167 ms |
| Jun 27, 2026 | 168 ms |
| Jul 4, 2026 | 170 ms |
| Jul 11, 2026 | 171 ms |
| Jul 18, 2026 | 170 ms |
| Jul 25, 2026 | 171 ms |
| Aug 1, 2026 | 175 ms |
| Aug 8, 2026 | 177 ms |
| Aug 15, 2026 | 180 ms |
| Aug 22, 2026 | 192 ms |
| Aug 29, 2026 | 196 ms |
| Sep 5, 2026 | 201 ms |
| Sep 12, 2026 | 204 ms |
| Sep 19, 2026 | 201 ms |
| Sep 26, 2026 | 206 ms |
| Oct 3, 2026 | 221 ms |
| Oct 10, 2026 | 229 ms |
| Oct 17, 2026 | 229 ms |
| Oct 24, 2026 | 229 ms |
| Oct 31, 2026 | 227 ms |
| Nov 7, 2026 | 227 ms |
| Nov 14, 2026 | 227 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
Main-thread work: 13.2 s
A phone's processor spends 13.2 s on main-thread work while loading, 6.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Render-blocking requests
1.1 s20 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Mobile performance score: 35
35/100Your mobile performance score is 35. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
4,117 HTML elements
The page has 4,117 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Klaviyo and Shopify and others), adding 2.7 MB and 2.2 s of main-thread time.
Reduce unused JavaScript
600 ms · 1.6 MBAbout 1.6 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.
Improve image delivery
1.1 MB17 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Use efficient cache lifetimes
643 KiB50 files are served with short cache lifetimes, so returning visitors download them again (643 KiB).
Google Tag Manager adds 411 ms
411 msGoogle Tag Manager costs a phone 411 ms of main-thread work and 600 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.
Klaviyo adds 361 ms
361 msKlaviyo costs a phone 361 ms of main-thread work and 540 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
150 ms · 255 KiBAbout 255 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Shopify adds 298 ms
298 msShopify costs a phone 298 ms of main-thread work and 483 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.
Truefit adds 278 ms
278 msTruefit costs a phone 278 ms of main-thread work and 629 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 275 ms. During a long task the page ignores taps.
Minify JavaScript
150 ms · 136 KiB136 KiB could be saved by minifying JavaScript.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
39 KiBPolyfills for old browsers add 39 KiB JavaScript that modern phones do not need.
Minify CSS
7 KiB7 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: 13 ms
13 msYour server sent the HTML in 13 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 39.5 s
39.5 sThe page becomes fully interactive after 39.5 s. Good is under 3.8 s.
Largest Contentful Paint: 8.6 s
8.6 sYour largest element takes 8.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 13.3 s
13.3 sVisually, the page fills in at 13.3 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 1.6 s
1.6 sScripts block taps and scrolling for 1.6 s in total while the page loads. Good is under 200 ms.
Tap response (INP) got 41% slower for real visitors
+41%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 161 ms to 227 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 29% slower for real visitors
+29%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.4 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 2.7 s
2.7 sThe first text or image appears after 2.7 s on a phone. Good is under 1.8 s.
7 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
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 INP: 152 ms
152 msReal visitors wait 152 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
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: 740 ms
740 msReal visitors wait 740 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.005
0.005The layout barely moves while loading (CLS 0.005, good is under 0.1).
Images and page weight
Page weight: 8.8 MB in 644 requests
8.8 MBYour homepage downloads 8.8 MB in 644 requests on a phone: scripts 4.2 MB (221), images 2.4 MB (40) and other files 1.6 MB (336). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
Fall-2024-Dresses-and-Gowns-Collection-Mac-Duggal-62988474.j 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).
1 image far larger than shown
16 KiB1 image is downloaded at several times the size a phone draws it, for example 56486-WIN-2059_2-Homepage.jpg at 600 px wide, shown at 167 px. Resized copies would save about 16 KiB.
About 2.5 g of CO₂ per visit
2.48 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.48 g of CO₂e: 298.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
13 buttons without a name
13 buttons have no accessible name, so screen readers announce just “button”.
8 tap targets too small
8 tap targets are too small or too close together to hit reliably with a finger.
Elements must only use permitted ARIA attributes (1 element)
Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.
24 images without alt text
24 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (4 elements)
All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.
12 form fields without a label
12 form fields have no label, so screen readers announce an empty box and autofill guesses.
10 links without text
10 visible links have no text or label, so screen readers cannot say where they go.
Alternative text of images should not be repeated as text (8 elements)
Alternative text of images should not be repeated as text: 8 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h5), which makes the page harder to scan with a screen reader.
1 checks passed
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 8 failed. 2 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 (“Holiday Dresses” and “Up to 70% Off Sale Styles”). One clear main headline is easier for people and search engines.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
2 links with vague text
2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
360 internal links, 16 external
The homepage links to 360 pages on macduggal.com and 16 external pages.
6 checks passed
Meta description: 151 characters
Your meta description is 151 characters: “Shop Mac Duggal luxury evening gowns, cocktail dresses, prom dresses, mother of the bride, and wedding guest styles in …”.
Title: 61 characters
Your title is a healthy 61 characters: “Mac Duggal Luxury Dresses - Evening Gowns, Cocktail & Wedding”.
Canonical URL set
The canonical URL is https://macduggal.com/.
Structured data in place
Structured data found: BreadcrumbList, MerchantReturnPolicy, Organization, SiteNavigationElement and WebPage.
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://macduggal.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://macduggal.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.
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.
Organization data: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (3,380 words), so crawlers that don't run JavaScript still read it.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 94 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 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=137008667&tm=gtm002&Ver=2&mid=7fccde6b-5404-4f93-ba3f-c455ec36f70d&bo=1&sid=d04b6850e43611f1be957b14538b530c&vid=d04bb840e43611f19e3937b3ba772c32&vids=1&msclkid=N>m_.
55 small tap targets
55 of 109 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Shopify is not defined”.
Missing source maps
Large scripts ship without source maps.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
Local business without LocalBusiness data
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.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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 614 words of copy
The homepage carries about 614 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP ALL” and “SHOP BY OCCASION”.
20 calls to action
The homepage has 20 calls to action, for example “Shop All”, “Shop By Occasion” and “Shop By Length”.
5 short forms
5 short forms (2 fields at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager and Microsoft Clarity.
Privacy and tracking
9 trackers load before any consent
9Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 4 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.
54 cookies set on arrival
54Opening the homepage sets 54 cookies, 3 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.
67 other companies contacted
Loading the homepage contacts 67 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 macduggal.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 15 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Consentmo Gdpr · Attentive · Analyzify Ga4 Ads Tracking · Microsoft Clarity · Minmaxify Order Limits · Klaviyo Email Marketing Sms · Mntn · Loop Returns · Gdpr Backpack · rakutenadvertising.io · nofraud.com · global-e.com · attn.tv · glopal.com · stamped.io
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
- The footer still says © 2024.
Stack
- E-commerce
- Shopify
- Analytics
- Google Tag Manager | Microsoft Clarity
- Hosting
- Shopify
Company
- Headquarters
- Ridge
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 43 issues on macduggal.com, including 21 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.