Masterpoweruae: a phone-and-desktop teardown
We loaded https://masterpoweruae.com/ 4 times on a simulated iPhone and 2 more on a 1366px desktop, and wrote down what a real visitor would see on each. No login, no insider access, no Harvv pixel needed. Here is what repeated visits already show, sorted by how we know it.
TL;DRWhat jumped out
Of everything we found on this scan, this is the one to start with: Tiny buttons are hard to tap on mobile. 36 of 40 tappable items on this page come in below 44×44 pixels, the minimum size Apple and Google recommend for reliable tapping, and the same ones came up small on every test load. When visitors can't hit what they expect to, they get frustrated and many of them leave instead of trying again.
Below: what's already working, every finding ranked by impact and tagged with the screen it affects, the speed numbers on phone and desktop, and a checklist of what to fix first.
00What's already working
Start here so the problems below are in context. These held up across the test loads:
- Speed is good. The main content paints in about 0.5s in our test loads, inside Google's 2.5s "good" threshold. Real networks are slower, but the page itself is not heavy.
- No JavaScript errors on load. Nothing threw a script error across the test loads, so buttons and tracking are not silently breaking mid-session.
- Search basics are in place. Lighthouse scores SEO 100/100. The fundamentals Google looks for are present.
- Layout holds on phone and desktop. Nothing spilled past the edge at either 390px (phone) or 1366px (desktop), so the structure is responsive.
01Findings, ranked by what hurts conversion most
| Severity | Finding | How we know |
|---|---|---|
| High | Tiny buttons are hard to tap on mobileMobileAccessibility (WCAG)Conversion 36 of 40 tappable items on this page come in below 44×44 pixels, the minimum size Apple and Google recommend for reliable tapping, and the same ones came up small on every test load. When visitors can't hit what they expect to, they get frustrated and many of them leave instead of trying again. | identical every load |
| High | A floating widget is covering a clickable elementBothConversionAccessibility (WCAG) A clickable element is sitting underneath a fixed overlay (div.container over a "Get a Quote"), so a visitor who tries to tap it hits the widget on top instead. The element is there and looks fine in a preview, it just can't be reached. Move the floating widget to a clear corner, lower its z-index, or add spacing so it never overlaps your links and buttons. The exact elements we found: | identical every load |
| High | Images without sizes set make the page jump as it loadsBothPerformanceSEO 2 of 3 images on this page don't have width and height set. As each image finishes loading, the content below it slides down to make room. The visitor goes to tap one thing and ends up tapping another, and the cause is invisible to them. The exact images we found: | identical every load |
| High | Some text is low-contrast and hard to readBothAccessibility (WCAG) Text that does not stand out enough from its background is hard to read for many visitors, and fails accessibility guidelines Google checks. | identical every load |
| Medium | Page is heavy and slow on mobile dataBothPerformance Each visit downloads about 3.2 megabytes, roughly 2683 KB of images and 2 KB of JavaScript across 14 separate downloads. On a fast connection that's fine. On a phone with patchy mobile data, that's several seconds of blank screen before the page is readable. | median across loads |
| Medium | 1 potential dead-click targetBothConversionAccessibility (WCAG)Tracking Elements styled like buttons but with no anchor, no <button> wrapper, no role="button", and no click attribute. Real visitors tap these expecting something to happen, then leave. Examples on this page: "Ready to Discuss Your Project? We " (div.container). The exact elements we found: | identical every load |
| Medium | No analytics installed, so you cannot see your own trafficBothTracking No Google Analytics, GA4, or any analytics tag was detected. There is no way to know how many visitors arrive, where they come from, or what converts, and no data to retarget or measure a campaign against. Installing GA4 (free) is the baseline. | identical every load |
| Low | Search-result title will be cut offBothSEO The title is 73 characters; Google truncates around 60. Front-load the important words so nothing useful gets clipped. | identical every load |
| Low | No email capture or newsletter detectedBothConversion No email-marketing tag (Klaviyo, Mailchimp, etc.) was found. Email capture plus a welcome and abandoned-cart flow is consistently the highest-ROI addition for a small store, and it is owned audience you keep regardless of ad costs. | identical every load |
| Low | No visible contact details (email or phone)BothConversion The page exposes no email or phone link. For higher-value or trust-sensitive purchases, a clear way to reach a human reduces hesitation. Add an email or phone link in the header or footer. | identical every load |
| Low | Unused CSS is being downloadedBothPerformance Style rules that this page never uses still block rendering while they download. Trimming them frees the paint path. Lighthouse measured: Est savings of 18 KiB. | identical every load |
| Low | Headings skip levelsBothAccessibility (WCAG) Jumping from an H1 straight to an H4 breaks the document outline that screen readers and search engines rely on. | identical every load |
| Low | No llms.txt fileBothSEO No /llms.txt. This emerging standard gives AI search engines a clean, structured map of your most important content, improving how they understand and cite your site. | identical every load |
| Low | No HSTS (Strict-Transport-Security)BothSEO No Strict-Transport-Security header on any crawled page. HSTS forces browsers to always use https for your domain, preventing protocol-downgrade and cookie-hijacking attacks. Add it to your server or CDN response headers. (Found across a sample of 1 pages from your sitemap, a partial crawl rather than your full site.) | identical every load |
Accessibility findings are automated checks against Web Content Accessibility Guidelines (WCAG) 2.1 and 2.2. They flag potential barriers and legal risk, not a certification or a determination of compliance with the ADA, Section 508, or EN 301 549. Automated testing catches only a subset of issues; a full conformance review needs manual and assistive-technology testing by a qualified reviewer.
"How we know": identical every load = a deterministic fact (e.g. element sizes). median across loads = a noisy lab metric, reported as a median. real-user field data = Google CrUX, actual Chrome visitors.
Structural and AI-search checks crawl up to 8 pages from your sitemap (a sample, not your full site). "Broken" means a link returned 404, 410, or 5xx, or did not respond; access-controlled pages (401, 403) are not counted.
02Performance: phone, desktop, and real visitors
| Metric | Mobile | Desktop | Read |
|---|---|---|---|
| TTFB (lab median) | 279 ms | 285 ms | Lab |
| FCP (lab median) | 504 ms | 522 ms | Lab |
| LCP (lab median) | 504 ms | 522 ms | Good |
| Page weight (median) | 3.2 MB | 3.1 MB | Watch |
Google Lighthouse (lab): Performance 85 mobile / 97 desktop, SEO 100, Accessibility 88, Best Practices 100.
Lab numbers are from a headless mobile browser on an unthrottled connection: treat them as a floor, not a typical experience. Add a Google API key to light up real-user field data (CrUX) and Lighthouse scores.
03Tiny buttons are hard to tap on mobile
36 of 40 tappable items on this page come in below 44×44 pixels, the size Apple and Google both recommend for reliable tapping on a phone. The same ones came up small on every one of the 4 test loads, so this is the page itself, not a fluke.
The buttons measuring below the minimum on this scan:
- a 206x33 "MasterPower Technical Servic"
- button 36x28 "Menu"
- button 24x10 "Item 1"
- button 10x10 "Item 2"
- button 10x10 "Item 3"
- button 10x10 "Item 4"
- button 10x10 "Item 5"
- button 10x10 "Item 6"
The fix is CSS-only on most sites: add padding around the icon (don't just change the icon size) so the actual tap area is at least 44×44 pixels. No redesign, no new assets.
04Technical SEO & structured data
| Check | Result |
|---|---|
| Title | MasterPower Technical Services LLC | MEP & Building Maintenance Dubai UAE (73 chars) |
| Meta description | 172 chars |
| H1 | 1 on page |
| Canonical | Present |
| Structured data (JSON-LD) | LocalBusiness |
| Open Graph | Title + image |
05The fix checklist
Everything to fix, priority first, each tagged with the screen it affects and a rough effort. Work top to bottom.
- Tiny buttons are hard to tap on mobileMobileCSS only
- A floating widget is covering a clickable elementBothCSS only
- Images without sizes set make the page jump as it loadsBothCSS only
- Some text is low-contrast and hard to readBothVaries
- Page is heavy and slow on mobile dataBothSmall
- 1 potential dead-click targetBothCSS only
- No analytics installed, so you cannot see your own trafficBothDev afternoon
- Search-result title will be cut offBoth1 line
- No email capture or newsletter detectedBothVaries
- No visible contact details (email or phone)BothVaries
- Unused CSS is being downloadedBothVaries
- Headings skip levelsBothVaries
- No llms.txt fileBothVaries
- No HSTS (Strict-Transport-Security)BothVaries
Effort is a rough read from the outside: "CSS only" means no new assets or backend work, "1 line" means a single tag, "Dev afternoon" means a developer needs to touch tracking or scripts.
06What this report cannot tell you
Everything above is from the outside, looking at the page on a simulated phone and desktop. The questions that actually decide revenue need real visitors. Install the Harvv pixel (one script tag, 16 KB, zero personal data, no engineering project) and within about 72 hours you'd know which buttons real customers tapped and missed, how often Google Analytics is missing visits, and exactly where mobile shoppers stalled and left. This report shows you where to look. The pixel shows you how often it happens, and to whom.
Drop the Harvv pixel on masterpoweruae.com and we turn this one-off scan into ongoing measured behavior: which taps miss, where sessions stall, and the real drop rates. Free to start, no card needed.
Add the pixel free07How we did this, and what it can't prove
- 4 mobile + 2 desktop loads of one URL from headless Chrome (iPhone viewport at 390px, desktop at 1366px), June 29, 2026. Enough loads to separate real defects from random noise, not a full-site crawl.
- Lab numbers, not real-user numbers (no field data was available for this run). Real devices on real networks run slower.
- Friction is inferred, not counted. We can prove a button is small. We can't, from the outside, count how often it causes a missed tap. That requires the pixel on a live page.
Prepared by Harvv. Last updated June 29, 2026.