Website review, no card needed

kenazperfumes.com logo

kenazperfumes.com website review

Visit site (opens in a new tab)Reviewed 4 November 202628 issues · 75 checks

This review found 28 issues worth fixing on kenazperfumes.com, 10 of them high impact, across 75 checks. The most urgent: fails Core Web Vitals for real visitors. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
4.2 s2.1 sMay 16Oct 312.3 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20263.7 s
May 23, 20263.7 s
May 30, 20263.8 s
Jun 6, 20263.9 s
Jun 13, 20264.0 s
Jun 20, 20263.8 s
Jun 27, 20263.6 s
Jul 4, 20263.4 s
Jul 11, 20263.3 s
Jul 18, 20263.3 s
Jul 25, 20263.3 s
Aug 1, 20263.3 s
Aug 8, 20263.3 s
Aug 15, 20263.3 s
Aug 22, 20263.3 s
Aug 29, 20263.2 s
Sep 5, 20263.2 s
Sep 12, 20263.2 s
Sep 19, 20263.3 s
Sep 26, 20263.2 s
Oct 3, 20263.0 s
Oct 10, 20262.7 s
Oct 17, 20262.4 s
Oct 24, 20262.3 s
Oct 31, 20262.3 s
Real-visitor tap response (INP)75th percentile, phones
316 ms236 msMay 16Oct 31302 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026252 ms
May 23, 2026253 ms
May 30, 2026254 ms
Jun 6, 2026254 ms
Jun 13, 2026257 ms
Jun 20, 2026257 ms
Jun 27, 2026256 ms
Jul 4, 2026254 ms
Jul 11, 2026250 ms
Jul 18, 2026247 ms
Jul 25, 2026245 ms
Aug 1, 2026246 ms
Aug 8, 2026248 ms
Aug 15, 2026249 ms
Aug 22, 2026247 ms
Aug 29, 2026246 ms
Sep 5, 2026248 ms
Sep 12, 2026254 ms
Sep 19, 2026262 ms
Sep 26, 2026277 ms
Oct 3, 2026290 ms
Oct 10, 2026299 ms
Oct 17, 2026307 ms
Oct 24, 2026301 ms
Oct 31, 2026302 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

Full-page screenshot of kenazperfumes.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. kenazperfumes.com at 0.4 s0.4 s
  2. kenazperfumes.com at 0.8 s0.8 s
  3. kenazperfumes.com at 1.1 s1.1 s
  4. kenazperfumes.com at 1.5 s1.5 s
  5. kenazperfumes.com at 1.9 s1.9 s
  6. kenazperfumes.com at 2.3 s2.3 s
  7. kenazperfumes.com at 2.6 s2.6 s
  8. kenazperfumes.com at 3.0 s3.0 s

Speed

4 to fix72
  • Mobile performance score: 72

    72/100

    Your mobile performance score is 72. Pages that score under 90 lose visitors before the first paint.

  • Render-blocking requests

    450 ms

    8 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.

  • 5 third-party services on the page

    5 third-party services load with your homepage (Google Fonts, Shopify and gokwik.co and others), adding 2.2 MB and 1 ms of main-thread time.

  • Shopify adds 0 ms

    0 ms

    Shopify costs a phone 0 ms of main-thread work and 2.1 MB 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.

  • Improve image delivery

    150 ms · 189 KiB

    11 images could be 189 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 137 ms. During a long task the page ignores taps.

  • Reduce unused CSS

    12 KiB

    About 12 KiB of CSS is downloaded but never applied on this page.

  • Use efficient cache lifetimes

    11 KiB

    2 files are served with short cache lifetimes, so returning visitors download them again (11 KiB).

  • 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.

2 checks passed
  • Main-thread work: 0.7 s

    A phone's processor spends 0.7 s on main-thread work while loading, 206 ms of it running JavaScript. That is comfortably low.

  • Server response: 18 ms

    18 ms

    Your server sent the HTML in 18 ms, well inside Google's 600 ms guideline.

Core Web Vitals

5 to fix67
  • 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: 10.5 s

    10.5 s

    Your largest element takes 10.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Time to Interactive: 10.6 s

    10.6 s

    The page becomes fully interactive after 10.6 s. Good is under 3.8 s.

  • Real-user INP: 281 ms

    281 ms

    Real visitors wait 281 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Speed Index: 4.1 s

    4.1 s

    Visually, the page fills in at 4.1 s (Speed Index). Good is under 3.4 s.

  • Tap response (INP) got 19% slower for real visitors

    +19%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 252 ms to 302 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

8 checks passed
  • Real-user LCP: 2.0 s

    2.0 s

    Real visitors wait 2.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user CLS: 0.02

    0.02

    For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.3 s

    1.3 s

    Real visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 454 ms

    454 ms

    Real visitors wait 454 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Largest content (LCP) got 37% faster for real visitors

    -37%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 3.7 s to 2.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • First Contentful Paint: 1.5 s

    1.5 s

    The first text or image appears after 1.5 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0.008

    0.008

    The layout barely moves while loading (CLS 0.008, good is under 0.1).

  • Total Blocking Time: 0 ms

    0 ms

    Scripts block the page for only 0 ms while loading. Good is under 200 ms.

Images and page weight

2 to fix81
  • Page weight: 4.0 MB in 125 requests

    4.0 MB

    Your homepage downloads 4.0 MB in 125 requests on a phone: media 2.1 MB (1), images 1.2 MB (45) and fonts 175 KiB (8). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    KENAZ_ARABIC_LOGOs-09_3.png 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).

  • About 1.1 g of CO₂ per visit

    1.13 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.13 g of CO₂e: 135.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

7 to fixGoogle 8290
  • Certain ARIA roles must contain particular children (5 elements)

    Certain ARIA roles must contain particular children: 5 elements on the page fail this check, rated critical by axe-core.

  • 10 tap targets too small

    10 tap targets are too small or too close together to hit reliably with a finger.

  • Scrollable region must have keyboard access (7 elements)

    Scrollable region must have keyboard access: 7 elements on the page fail this check, rated serious by axe-core.

  • Hidden but focusable

    1 element hidden from screen readers can still receive keyboard focus.

  • 8 images without alt text

    8 images have no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 11 links without text

    11 visible links have no text or label, so screen readers cannot say where they go.

1 checks passed
  • 53 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 60 WCAG 2.2 A/AA and best-practice rules on the phone render: 53 passed and 7 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 8575
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • Title is short (14 characters)

    Your title is only 14 characters: “Kenaz Perfumes”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 3 H1 headlines

    There are 3 <h1> headlines (“Vibe Check”, “” and “Our Best Sellers”). 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.

  • 65 internal links, 6 external

    The homepage links to 65 pages on kenazperfumes.com and 6 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://kenazperfumes.com/.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • 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://kenazperfumes.com/sitemap.xml.

AI search readiness

100
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: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (570 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://kenazperfumes.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

1 to fix95
  • 9 pages without a meta description

    https://kenazperfumes.com/collections/all-products, https://kenazperfumes.com/products/ultimate-dubai-box, https://kenazperfumes.com/products/pocket-trio, https://kenazperfumes.com/products/dubai-trio, https://kenazperfumes.com/collections/first-collection and https://kenazperfumes.com/collections/second-collection and 3 others 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 28 found) and read each the way a search engine does.

6 checks passed
  • Linked pages load

    14 pages of 15 loaded without an error (the rest turned automated requests away).

  • 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 to fixGoogle 9285
  • 16 small tap targets

    16 of 37 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “window is not defined”.

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • 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 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 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 348 words of copy

    The homepage carries about 348 words of visible text.

4 checks passed
  • 5 calls to action

    The homepage has 5 calls to action, for example “Shop All”, “contact us” and “Shop Now”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 40 testimonial or review blocks and 2 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Microsoft Clarity.

Privacy and tracking

  • 4 cookies set on arrival

    4

    Opening the homepage sets 4 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.

  • 6 other companies contacted

    Loading the homepage contacts 6 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 kenazperfumes.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

E-commerce
Shopify
Analytics
Google Analytics | Google Tag Manager | Microsoft Clarity
Hosting
Shopify

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 28 issues on kenazperfumes.com, including 9 speed issues, 4 SEO issues and 2 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25