Website review, no card needed

portalsparfums.com logo

portalsparfums.com website review

Visit site (opens in a new tab)Reviewed 8 November 202633 issues · 78 checks

This review found 33 issues worth fixing on portalsparfums.com, 6 of them high impact, across 78 checks. The most urgent: 1 text element with low contrast. 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
1.1 s822 msMay 16Oct 311.0 s
Show as table
DateReal-visitor load time (LCP)
May 16, 2026853 ms
May 23, 2026859 ms
May 30, 2026870 ms
Jun 6, 2026858 ms
Jun 13, 2026852 ms
Jun 20, 2026851 ms
Jun 27, 2026856 ms
Jul 4, 2026870 ms
Jul 11, 2026869 ms
Jul 18, 2026877 ms
Jul 25, 2026872 ms
Aug 1, 2026870 ms
Aug 8, 2026882 ms
Aug 15, 2026862 ms
Aug 22, 2026873 ms
Aug 29, 2026994 ms
Sep 5, 20261.0 s
Sep 12, 20261.0 s
Sep 19, 20261.0 s
Sep 26, 20261.0 s
Oct 3, 20261.0 s
Oct 10, 20261.0 s
Oct 17, 20261.0 s
Oct 24, 20261.0 s
Oct 31, 20261.0 s
Real-visitor tap response (INP)75th percentile, phones
127 ms100 msMay 16Oct 31121 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026103 ms
May 23, 2026104 ms
May 30, 2026105 ms
Jun 6, 2026104 ms
Jun 13, 2026106 ms
Jun 20, 2026107 ms
Jun 27, 2026108 ms
Jul 4, 2026111 ms
Jul 11, 2026111 ms
Jul 18, 2026111 ms
Jul 25, 2026110 ms
Aug 1, 2026110 ms
Aug 8, 2026111 ms
Aug 15, 2026111 ms
Aug 22, 2026113 ms
Aug 29, 2026121 ms
Sep 5, 2026121 ms
Sep 12, 2026123 ms
Sep 19, 2026124 ms
Sep 26, 2026124 ms
Oct 3, 2026123 ms
Oct 10, 2026124 ms
Oct 17, 2026122 ms
Oct 24, 2026121 ms
Oct 31, 2026121 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 portalsparfums.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. portalsparfums.com at 0.6 s0.6 s
  2. portalsparfums.com at 1.1 s1.1 s
  3. portalsparfums.com at 1.7 s1.7 s
  4. portalsparfums.com at 2.2 s2.2 s
  5. portalsparfums.com at 2.8 s2.8 s
  6. portalsparfums.com at 3.4 s3.4 s
  7. portalsparfums.com at 3.9 s3.9 s
  8. portalsparfums.com at 4.5 s4.5 s

Speed

6 to fix66
  • Mobile performance score: 66

    66/100

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

  • Reduce unused JavaScript

    640 ms · 130 KiB

    About 130 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 640 ms faster on a phone.

  • Improve image delivery

    200 ms · 393 KiB

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

  • Legacy JavaScript

    450 ms · 19 KiB

    Polyfills for old browsers add 19 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 450 ms faster on a phone.

  • Render-blocking requests

    350 ms

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

  • Klaviyo adds 133 ms

    133 ms

    Klaviyo costs a phone 133 ms of main-thread work and 308 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.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Klaviyo, Shopify and 9gtb.com and others), adding 651 KiB and 284 ms of main-thread time.

  • Use efficient cache lifetimes

    250 ms · 90 KiB

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

  • 3 long tasks on the main thread

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

  • Reduce unused CSS

    23 KiB

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

  • 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: 1.6 s

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

  • Server response: 6 ms

    6 ms

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

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 10.7 s

    10.7 s

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

  • Time to Interactive: 11.2 s

    11.2 s

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

  • Speed Index: 6.2 s

    6.2 s

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

  • First Contentful Paint: 2.5 s

    2.5 s

    The first text or image appears after 2.5 s on a phone. Good is under 1.8 s.

  • 5 images without width and height

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

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

    +17%

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

  • Largest content (LCP) got 19% slower for real visitors

    +19%

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

8 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: 1.2 s

    1.2 s

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

  • Real-user INP: 105 ms

    105 ms

    Real visitors wait 105 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: 1.1 s

    1.1 s

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

  • Real-user TTFB: 751 ms

    751 ms

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

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 10 ms

    10 ms

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

Images and page weight

2 to fix75
  • Page weight: 2.3 MB in 197 requests

    2.3 MB

    Your homepage downloads 2.3 MB in 197 requests on a phone: other files 746 KiB (93), scripts 741 KiB (74) and images 614 KiB (15). Under 2 MB keeps phones on slow connections fast.

  • 4 images far larger than shown

    206 KiB

    4 images are downloaded at several times the size a phone draws them, for example BodySpray_Collection_1000x1000.jpg at 903 px wide, shown at 194 px. Resized copies would save about 206 KiB.

  • 2 images below the first screen load straight away

    2 images further down the page (159 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.66 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

7 to fixGoogle 9292
  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 4 images without alt text

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

  • Banner landmark should not be contained in another landmark (2 elements)

    Banner landmark should not be contained in another landmark: 2 elements on the page fail this check, rated moderate by axe-core.

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

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

  • Document should not have more than one banner landmark (1 element)

    Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

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

  • 10 links without text

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

1 checks passed
  • 46 automated accessibility rules passed

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

SEO

5 to fixGoogle 9282
  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 3 H1 headlines

    There are 3 <h1> headlines (“”, “” and “Your cart”). One clear main headline is easier for people and search engines.

  • Meta description is long (206 characters)

    Your meta description is 206 characters; Google truncates after about 160, so the end of your pitch is cut.

  • No social preview image

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

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • 62 internal links, 9 external

    The homepage links to 62 pages on portalsparfums.com and 9 external pages.

4 checks passed
  • Title: 35 characters

    Your title is a healthy 35 characters: “Portals Parfums by Melanie Martinez”.

  • Canonical URL set

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

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

AI search readiness

1 to fix88
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

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

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

2 to fix90
  • 1 page without a meta description

    https://portalsparfums.com/products/cry_baby has no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://portalsparfums.com/collections/fragrances and https://portalsparfums.com/collections/body-sprays 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 50 found) and read each the way a search engine does.

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

2 checks passed
  • Tap targets are thumb-sized

    15 of 16 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix71
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

  • Only about 194 words

    The homepage has only about 194 words of visible text; thin pages give Google and first-time buyers little to go on.

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

4 checks passed
  • Clear next step on the first screen

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

  • 12 calls to action

    The homepage has 12 calls to action, for example “Shop All”, “SHOP NOW” and “SHOP ALL”.

  • 2 short forms

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

  • Analytics in place

    Analytics detected: Microsoft Clarity.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

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

  • 21 cookies set on arrival

    21

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

  • 30 other companies contacted

    Loading the homepage contacts 30 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 portalsparfums.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

Pandectes Gdpr · Geo Pro Geolocation · Klaviyo Email Marketing Sms · Minmaxify Order Limits · Gdpr Cookie Consent · Easylocation · Accessibly App · Restockrocket · gorgias.chat · 9gtb.com

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
Tailwind CSS
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 33 issues on portalsparfums.com, including 11 speed issues, 5 SEO issues and 3 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