Ifadvisory: a phone-and-desktop teardown
We loaded https://ifadvisory.org/ 4 times on a simulated iPhone and 2 more on a 1366px desktop, and wrote down what a real visitor would see on each, then cross-checked it against real Chrome users from Google's field data. 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: Images without sizes set make the page jump as it loads. 80 of 80 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.
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. Real Chrome visitors see the main content in 1.3s (Google's "good" bar is 2.5s). This is field data from actual users, not a lab guess.
- Light page weight. The page is about 1.1 MB across 72 requests. That keeps it quick on mobile data and cheap to load repeatedly.
- Layout stays put as it loads. Real visitors see only 0.00 of layout shift (good is under 0.10), so the page is not jumping under their finger.
- 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 | Images without sizes set make the page jump as it loadsBothPerformanceSEO 80 of 80 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. | identical every load |
| High | 10 interactive elements have no stable, accessible identityBothAccessibility (WCAG)Tracking These elements are clicked like buttons but expose no accessible name, or are a plain div/span used as a control with no role. Assistive tech announces only a role (or nothing), and analytics and heatmaps have no human-readable label or stable selector to bind the click to, so the click is both inaccessible and untrackable, and any redesign silently breaks click aggregation. Give each one a real <button>/<a>, an aria-label, and a stable id or data-attribute. The exact elements 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 | 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: "Cohort 1 — Sold Out" (div.EduPromo-module__Otrzdq__pill). 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 | No canonical tag, so duplicate URLs split the page's rankingBoth When the same content is reachable at multiple URLs (think tracking parameters or session IDs), Google can split your ranking signal across them. A single canonical tag tells Google which version counts. | 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 | Unused JavaScript is being downloadedBothPerformance Code that never runs on this page still costs download and parse time on every visit. Splitting or removing it speeds up load. Lighthouse measured: Est savings of 27 KiB. | 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 14 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 |
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) | 26 ms | 16 ms | Lab |
| FCP (lab median) | 188 ms | 226 ms | Lab |
| LCP (lab median) | 188 ms | 226 ms | Good |
| Page weight (median) | 1.1 MB | 1.1 MB | OK |
| Real LCP (p75, origin) | 1.3 s | Good | |
| Real INP (p75) | n/a | ||
| Real CLS (p75) | 0.00 | Good | |
Google Lighthouse (lab): Performance 74 mobile / 68 desktop, SEO 100, Accessibility 94, Best Practices 100.
Lab numbers are from a headless mobile browser on an unthrottled connection: treat them as a floor, not a typical experience.
03Tiny buttons are hard to tap on mobile
24 of 67 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:
- button 42x42 "Open menu"
- a 271x21 "ORGANISATIONS WE'VE WORKED W"
- a 136x18 "Shari'ah Consultancy"
- a 122x18 "Dispute Resolution"
- a 73x18 "Investment"
- a 116x18 "Zakah Calculation"
- a 121x18 "Wills & Inheritance"
- a 123x18 "Business & Finance"
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 | Islamic Finance Advisory (24 chars) |
| Meta description | 155 chars |
| H1 | 1 on page |
| Canonical | Missing |
| Structured data (JSON-LD) | Organization |
| 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.
- Images without sizes set make the page jump as it loadsBothCSS only
- 10 interactive elements have no stable, accessible identityBothDev afternoon
- Some text is low-contrast and hard to readBothVaries
- 1 potential dead-click targetBothCSS only
- No analytics installed, so you cannot see your own trafficBothDev afternoon
- No canonical tag, so duplicate URLs split the page's rankingBoth1 line
- No email capture or newsletter detectedBothVaries
- Unused JavaScript is being downloadedBothVaries
- Unused CSS is being downloadedBothVaries
- Headings skip levelsBothVaries
- No llms.txt fileBothVaries
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 ifadvisory.org 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, except the CrUX rows, which are real Chrome users. 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.