Website review, no card needed

replikascent.com logo

replikascent.com website review

Visit site (opens in a new tab)Reviewed 7 November 202627 issues · 77 checks

This review found 27 issues worth fixing on replikascent.com, 5 of them high impact, across 77 checks. The most urgent: render-blocking requests. 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
979 ms729 msMay 16Oct 31758 ms
Show as table
DateReal-visitor load time (LCP)
May 16, 2026933 ms
May 23, 2026932 ms
May 30, 2026896 ms
Jun 6, 2026871 ms
Jun 13, 2026878 ms
Jun 20, 2026913 ms
Jun 27, 2026950 ms
Jul 4, 2026947 ms
Jul 11, 2026947 ms
Jul 18, 2026911 ms
Jul 25, 2026878 ms
Aug 1, 2026884 ms
Aug 8, 2026876 ms
Aug 15, 2026895 ms
Aug 22, 2026909 ms
Aug 29, 2026880 ms
Sep 5, 2026866 ms
Sep 12, 2026867 ms
Sep 19, 2026856 ms
Sep 26, 2026852 ms
Oct 3, 2026844 ms
Oct 10, 2026822 ms
Oct 17, 2026817 ms
Oct 24, 2026782 ms
Oct 31, 2026758 ms
Real-visitor tap response (INP)75th percentile, phones
142 ms90 msMay 16Oct 31136 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026103 ms
May 23, 202697 ms
May 30, 2026100 ms
Jun 6, 2026103 ms
Jun 13, 202696 ms
Jun 20, 2026103 ms
Jun 27, 2026104 ms
Jul 4, 2026104 ms
Jul 18, 2026103 ms
Jul 25, 202697 ms
Aug 1, 202697 ms
Aug 8, 2026103 ms
Aug 15, 2026104 ms
Aug 22, 2026113 ms
Aug 29, 2026112 ms
Sep 5, 2026119 ms
Sep 12, 2026123 ms
Sep 19, 2026124 ms
Sep 26, 2026130 ms
Oct 3, 2026129 ms
Oct 10, 2026128 ms
Oct 17, 2026130 ms
Oct 24, 2026130 ms
Oct 31, 2026136 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 replikascent.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

4 to fix92
  • Render-blocking requests

    1.1 s

    6 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.

  • Reduce unused CSS

    300 ms · 57 KiB

    About 57 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

  • Improve image delivery

    300 ms · 52 KiB

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

  • Main-thread work: 2.2 s

    A phone's processor spends 2.2 s on main-thread work while loading, 1.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Clarity, Klaviyo and loox.io and others), adding 723 KiB and 298 ms of main-thread time.

  • Reduce unused JavaScript

    216 KiB

    About 216 KiB of JavaScript is downloaded but never used on this page.

  • 2 long tasks on the main thread

    2 long tasks block the main thread while loading, the longest for 95 ms. During a long task the page ignores taps.

  • Use efficient cache lifetimes

    31 KiB

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

  • Legacy JavaScript

    30 KiB

    Polyfills for old browsers add 30 KiB JavaScript that modern phones do not need.

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

  • Minify CSS

    2 KiB

    2 KiB could be saved by minifying CSS.

2 checks passed
  • Mobile performance score: 92

    92/100

    Your mobile performance score is 92. That is in Google's “good” band (90 and up).

  • Server response: 8 ms

    8 ms

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

Core Web Vitals

5 to fix100
  • Tap response (INP) got 33% slower for real visitors

    +33%

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

  • Time to Interactive: 6.5 s

    6.5 s

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

  • Largest Contentful Paint: 3.2 s

    3.2 s

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

  • Speed Index: 3.7 s

    3.7 s

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

  • 2 images without width and height

    2 images have no width and height attributes, so the layout jumps as each one loads.

10 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: 0.8 s

    0.8 s

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

  • Real-user INP: 119 ms

    119 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 0.8 s

    0.8 s

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

  • Real-user TTFB: 559 ms

    559 ms

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

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

    -17%

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

  • Cumulative Layout Shift: 0

    0

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

  • First Contentful Paint: 1.1 s

    1.1 s

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

  • Total Blocking Time: 31 ms

    31 ms

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

Images and page weight

2 to fix81
  • Page weight: 3.1 MB in 198 requests

    3.1 MB

    Your homepage downloads 3.1 MB in 198 requests on a phone: fonts 1.1 MB (7), other files 974 KiB (100) and scripts 612 KiB (67). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    Saffron_Bliss.jpg 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 in older formats

    2 images (59 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.

  • About 0.9 g of CO₂ per visit

    0.88 g

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

1 checks passed
  • Images are sized for phones

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

Accessibility

4 to fixGoogle 9595
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 2 images without alt text

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • ARIA role should be appropriate for the element (3 elements)

    ARIA role should be appropriate for the element: 3 elements on the page fail this check, rated minor by axe-core.

1 checks passed
  • 51 automated accessibility rules passed

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

SEO

2 to fixGoogle 10092
  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • One H1 headline

    Your <h1> is empty.

  • 40 internal links, 0 external

    The homepage links to 40 pages on replikascent.com and 0 external pages.

6 checks passed
  • Meta description: 121 characters

    Your meta description is 121 characters: “Experience premier alternatives to iconic designer fragrances—crafted sustainably and transparently, minus the brand ta…”.

  • Title: 55 characters

    Your title is a healthy 55 characters: “Replika Scent - Luxury Scents, Without the Luxury Price”.

  • Canonical URL set

    The canonical URL is https://replikascent.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://replikascent.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 (652 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

5 to fix67
  • 1 page without a title

    https://replikascent.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

  • 1 linked page hidden from search

    https://replikascent.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 8 pages without a meta description

    https://replikascent.com/pages/reviews, https://replikascent.com/pages/contact-us, https://replikascent.com/pages/track-order, https://replikascent.com/customer_authentication/redirect, https://replikascent.com/collections/all and https://replikascent.com/collections/perfume and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 6 pages share a meta description

    https://replikascent.com/products/bundle-and-save and https://replikascent.com/products/perfume use the same meta description. A description written for each page earns more clicks.

  • 7 pages without an H1

    https://replikascent.com/pages/contact-us, https://replikascent.com/pages/track-order, https://replikascent.com/customer_authentication/redirect, https://replikascent.com/collections/all, https://replikascent.com/collections/perfume and https://replikascent.com/products/bundle-and-save and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 19 found) and read each the way a search engine does.

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

  • Titles are unique

    Every page we checked has its own title.

Best practices

3 to fixGoogle 9671
  • 1 broken image

    1 image failed to load on a phone, for example https://www.laifentech.com/cdn/shop/t/97/assets/shield.png?v=90651786104336064811708060166.

  • 4 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix93
  • 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.

  • About 543 words of copy

    The homepage carries about 543 words of visible text.

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP NOW”.

  • 10 calls to action

    The homepage has 10 calls to action, for example “Contact Us”, “Track Order” and “Shop All”.

  • 4 short forms

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

  • Social proof on the page

    Social proof on the homepage: 14 testimonial or review blocks, a star rating, 1 trust badge and “1,000+ reviews”.

  • Analytics in place

    Analytics detected: Microsoft Clarity.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Tag Manager, Klaviyo, Meta Pixel and Microsoft Clarity (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.

  • 18 cookies set on arrival

    18

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

  • 32 other companies contacted

    Loading the homepage contacts 32 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 replikascent.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 8 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Intelligems A B Testing · Klaviyo Email Marketing Sms · Kaching Bundles · Microsoft Clarity · Triplewhale · Skio Subscriptions Yc S20 · Gift Box Builder · loox.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

Stack

Framework
jQuery
E-commerce
Shopify
Analytics
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 27 issues on replikascent.com, including 9 speed issues, 2 SEO issues and 1 conversion gap. 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