Website review, no card needed
fawwaha.com website review
Visit site (opens in a new tab)Reviewed 6 November 202634 issues · 81 checks
This review found 34 issues worth fixing on fawwaha.com, 11 of them high impact, across 81 checks. The most urgent: reduce unused JavaScript. 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
84B- #21,583 of 120,317 reviewed websitesbeats 77%
- #13,998 of 68,134 online storesbeats 73%
- #13,581 of 62,091 Shopify storesbeats 72%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.5 s |
| May 23, 2026 | 2.6 s |
| May 30, 2026 | 2.6 s |
| Jun 6, 2026 | 2.6 s |
| Jun 13, 2026 | 2.6 s |
| Jun 20, 2026 | 2.6 s |
| Jun 27, 2026 | 2.6 s |
| Jul 4, 2026 | 2.6 s |
| Jul 11, 2026 | 2.5 s |
| Jul 18, 2026 | 2.6 s |
| Jul 25, 2026 | 2.6 s |
| Aug 1, 2026 | 2.5 s |
| Aug 8, 2026 | 2.4 s |
| Aug 15, 2026 | 2.3 s |
| Aug 22, 2026 | 2.3 s |
| Aug 29, 2026 | 2.5 s |
| Sep 5, 2026 | 2.9 s |
| Sep 12, 2026 | 3.4 s |
| Sep 19, 2026 | 3.7 s |
| Sep 26, 2026 | 3.3 s |
| Oct 3, 2026 | 2.9 s |
| Oct 10, 2026 | 2.5 s |
| Oct 17, 2026 | 2.2 s |
| Oct 24, 2026 | 2.2 s |
| Oct 31, 2026 | 2.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 170 ms |
| May 23, 2026 | 178 ms |
| May 30, 2026 | 189 ms |
| Jun 6, 2026 | 199 ms |
| Jun 13, 2026 | 202 ms |
| Jun 20, 2026 | 201 ms |
| Jun 27, 2026 | 203 ms |
| Jul 4, 2026 | 203 ms |
| Jul 11, 2026 | 203 ms |
| Jul 18, 2026 | 199 ms |
| Jul 25, 2026 | 195 ms |
| Aug 1, 2026 | 193 ms |
| Aug 8, 2026 | 194 ms |
| Aug 15, 2026 | 194 ms |
| Aug 22, 2026 | 196 ms |
| Aug 29, 2026 | 201 ms |
| Sep 5, 2026 | 205 ms |
| Sep 12, 2026 | 217 ms |
| Sep 19, 2026 | 221 ms |
| Sep 26, 2026 | 223 ms |
| Oct 3, 2026 | 220 ms |
| Oct 10, 2026 | 213 ms |
| Oct 17, 2026 | 209 ms |
| Oct 24, 2026 | 207 ms |
| Oct 31, 2026 | 211 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.9 s
1.7 s
2.6 s
3.5 s
4.3 s
5.2 s
6.0 s
6.9 s
Speed
Reduce unused JavaScript
1.0 s · 243 KiBAbout 243 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.0 s faster on a phone.
Render-blocking requests
1.2 s4 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.2 s.
Mobile performance score: 62
62/100Your mobile performance score is 62. Pages that score under 90 lose visitors before the first paint.
8 third-party services on the page
8 third-party services load with your homepage (ContentSquare, Shopify and JSDelivr CDN and others), adding 623 KiB and 547 ms of main-thread time.
ContentSquare adds 346 ms
346 msContentSquare costs a phone 346 ms of main-thread work and 168 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.
Main-thread work: 3.0 s
A phone's processor spends 3.0 s on main-thread work while loading, 1.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Shopify adds 181 ms
181 msShopify costs a phone 181 ms of main-thread work and 393 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.
2,056 HTML elements
The page has 2,056 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
163 KiB4 images could be 163 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Use efficient cache lifetimes
150 ms · 10 KiB3 files are served with short cache lifetimes, so returning visitors download them again (10 KiB).
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 87 ms. During a long task the page ignores taps.
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: 9 ms
9 msYour server sent the HTML in 9 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.
Largest Contentful Paint: 9.3 s
9.3 sYour largest element takes 9.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 7.3 s
7.3 sVisually, the page fills in at 7.3 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 9.5 s
9.5 sThe page becomes fully interactive after 9.5 s. Good is under 3.8 s.
First Contentful Paint: 3.2 s
3.2 sThe first text or image appears after 3.2 s on a phone. Good is under 1.8 s.
Tap response (INP) got 20% slower for real visitors
+20%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 170 ms to 211 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.0 s
2.0 sReal visitors see the first content after 2.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.2 s
1.2 sReal visitors wait 1.2 s for your server to start answering (75th percentile). Good is under 800 ms.
15 images without width and height
15 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
-7%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.5 s to 2.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 2.2 s
2.2 sReal visitors wait 2.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 183 ms
183 msReal visitors wait 183 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.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 41 ms
41 msScripts block the page for only 41 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 2.6 MB in 316 requests
2.6 MBYour homepage downloads 2.6 MB in 316 requests on a phone: other files 1.1 MB (193), images 743 KiB (24) and scripts 616 KiB (67). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
baner.webp 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).
2 images far larger than shown
86 KiB2 images are downloaded at several times the size a phone draws them, for example turkish_perfume.jpg at 800 px wide, shown at 165 px. Resized copies would save about 86 KiB.
3 images in older formats
3 images (195 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.
3 images below the first screen load straight away
3 images further down the page (73 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.7 g of CO₂ per visit
0.75 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.75 g of CO₂e: 89.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
15 text elements with low contrast
15 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Elements must only use permitted ARIA attributes (2 elements)
Elements must only use permitted ARIA attributes: 2 elements on the page fail this check, rated serious by axe-core.
Scrollable region must have keyboard access (2 elements)
Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.
Alternative text of images should not be repeated as text (5 elements)
Alternative text of images should not be repeated as text: 5 elements on the page fail this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 52 images in the HTML carry an alt attribute.
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 4 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is long (235 characters)
Your meta description is 235 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 2 problems
Structured data found (Organization, WebPage and WebSite) but with 2 problems, for example “Organization: logo is not an absolute URL ("//www.fawwaha.com/cdn/shop/files/logo_fawwaha.jpg?v=161…”.
One H1 headline
Your <h1> is empty.
98 internal links, 8 external
The homepage links to 98 pages on fawwaha.com and 8 external pages.
5 checks passed
Title: 56 characters
Your title is a healthy 56 characters: “A Premium Perfume Brand in Pakistan – Fawwaha Fragrances”.
Canonical URL set
The canonical URL is https://www.fawwaha.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://www.fawwaha.com/sitemap.xml.
AI search readiness
4 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: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, description and contact details; sameAs (social profiles) would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (823 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.fawwaha.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 linked page is broken
Your homepage links to https://www.fawwaha.com/pages/return-exchange-policy, which answers with an error. Visitors hit a dead end and search engines drop it.
3 pages without a meta description
https://www.fawwaha.com/collections/all, https://www.fawwaha.com/collections/prestige-collection and https://www.fawwaha.com/collections/women-fragrances have no meta description, so Google writes the search snippet from whatever text it finds.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 53 found) and read each the way a search engine does.
5 checks passed
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
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 14 pages that loaded have a <title>.
Best practices
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
21 of 25 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 573 words of copy
The homepage carries about 573 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: “Contact us”.
10 calls to action
The homepage has 10 calls to action, for example “Shop”, “Contact” and “Contact Us”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 123 testimonial or review blocks and a star rating.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity 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.
24 cookies set on arrival
24Opening the homepage sets 24 cookies (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.
29 other companies contacted
Loading the homepage contacts 29 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 fawwaha.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 10 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
King Product Options · Ez Ai Seo Optimizer · Mergn · Ck Whatsapp · Contentsquare Analytics · Judge Me Reviews · Whatsapp Abandoned Cart · Scala Discounts · Selleasy · Vizup
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
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 34 issues on fawwaha.com, including 17 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.