Website review, no card needed

volantaroma.com logo

volantaroma.com website review

Visit site (opens in a new tab)Reviewed 6 November 202628 issues · 76 checks

This review found 28 issues worth fixing on volantaroma.com, 7 of them high impact, across 76 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
2.2 s1.8 sMay 16Aug 11.9 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.1 s
May 23, 20262.1 s
May 30, 20262.1 s
Jun 6, 20262.1 s
Jun 13, 20262.0 s
Jun 20, 20262.0 s
Jun 27, 20262.0 s
Jul 11, 20262.0 s
Jul 18, 20261.8 s
Aug 1, 20261.9 s
Real-visitor tap response (INP)75th percentile, phones
114 ms101 msMay 16Jun 27111 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026112 ms
May 23, 2026111 ms
May 30, 2026109 ms
Jun 6, 2026104 ms
Jun 13, 2026102 ms
Jun 20, 2026102 ms
Jun 27, 2026111 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 volantaroma.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

5 to fix69
  • Render-blocking requests

    1.7 s

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

  • Reduce unused JavaScript

    600 ms · 468 KiB

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

  • Mobile performance score: 69

    69/100

    Your mobile performance score is 69. 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 (Google Tag Manager, OptiMonk and Klaviyo and others), adding 1.4 MB and 564 ms of main-thread time.

  • Use efficient cache lifetimes

    450 ms · 234 KiB

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

  • Reduce unused CSS

    150 ms · 75 KiB

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

  • Legacy JavaScript

    150 ms · 59 KiB

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

  • 4 long tasks on the main thread

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

  • Improve image delivery

    96 KiB

    2 images could be 96 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • Duplicated JavaScript

    37 KiB

    37 KiB JavaScript is shipped twice across bundles.

  • 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

    4 KiB

    4 KiB could be saved by minifying CSS.

2 checks passed
  • Main-thread work: 1.9 s

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

  • Server response: 5 ms

    5 ms

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

Core Web Vitals

4 to fix64
  • Largest Contentful Paint: 8.2 s

    8.2 s

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

  • Time to Interactive: 17.4 s

    17.4 s

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

  • First Contentful Paint: 2.3 s

    2.3 s

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

  • 17 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -4%

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

4 checks passed
  • Largest content (LCP) got 11% faster for real visitors

    -11%

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

  • Speed Index: 3.3 s

    3.3 s

    Visually, the page fills in at 3.3 s (Speed Index), inside the 3.4 s “good” threshold.

  • Total Blocking Time: 198 ms

    198 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix75
  • Page weight: 3.3 MB in 338 requests

    3.3 MB

    Your homepage downloads 3.3 MB in 338 requests on a phone: scripts 1.5 MB (102), other files 1.0 MB (176) and images 358 KiB (32). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    66 KiB

    1 image is downloaded at several times the size a phone draws it, for example Focus_essential_oil_along_with_some_other_herbs_600x_04624ee at 600 px wide, shown at 105 px. Resized copies would save about 66 KiB.

  • 1 image below the first screen load straight away

    1 image further down the page (90 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 0.9 g of CO₂ per visit

    0.93 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.93 g of CO₂e: 111.7 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

5 to fixGoogle 8392
  • 2 text elements with low contrast

    2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

  • 25 images without alt text

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

1 checks passed
  • 48 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: 48 passed and 5 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 9295
  • Meta description is long (258 characters)

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

  • 46 internal links, 20 external

    The homepage links to 46 pages on volantaroma.com and 20 external pages.

7 checks passed
  • One H1 headline

    Your main headline reads: “Volant Europe”.

  • Title: 35 characters

    Your title is a healthy 35 characters: “volant | Essential Oils & Diffusers”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, Organization and WebSite.

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

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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 (350 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

4 to fix73
  • 1 page points its canonical at the homepage

    https://volantaroma.com/products/volant-diffuser declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

  • 2 pages share a title

    / and https://volantaroma.com/products/volant-diffuser all use the title “volant | Essential Oils & Diffusers”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 6 pages without a meta description

    https://volantaroma.com/collections/archive-sale, https://volantaroma.com/collections/zodiac-blends, https://volantaroma.com/pages/about-aromatherapy, https://volantaroma.com/collections/all, https://volantaroma.com/pages/media and https://volantaroma.com/pages/store-locator have no meta description, so Google writes the search snippet from whatever text it finds.

  • 12 pages without an H1

    https://volantaroma.com/collections/all-products, https://volantaroma.com/collections/archive-sale, https://volantaroma.com/collections/essential-oils, https://volantaroma.com/collections/essential-oil-sets, https://volantaroma.com/collections/zodiac-blends and https://volantaroma.com/pages/aboutus and 6 others 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 17 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.

  • 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

3 to fixGoogle 6985
  • 3 small tap targets

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

  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “[Weglot] Cannot load Weglot because the project has been deleted”.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix88
  • 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 152 words

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

6 checks passed
  • Clear next step on the first screen

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

  • 6 calls to action

    The homepage has 6 calls to action, for example “Start shopping”, “Shop All” and “SHOP FINAL STOCK”.

  • 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: 2 testimonial or review blocks and 6 customer or partner logos.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • 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
  • 7 trackers load before any consent

    7

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

  • 28 cookies set on arrival

    28

    Opening the homepage sets 28 cookies, 1 of them by other companies (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.

  • 48 other companies contacted

    Loading the homepage contacts 48 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 volantaroma.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

Pagefly Ai Page Builder · Optimonk Popup Cro A B Test · Klaviyo Email Marketing Sms · Revenuehunt · jsdelivr.net · weglot.com · snapchat.com · trustpilot.com · cloudwaysapps.com · amazonaws.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
jQuery
E-commerce
Shopify
Analytics
Google Analytics | Google Tag Manager
Hosting
Shopify

Company

Headquarters
Oslo

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 volantaroma.com, including 9 speed issues, 1 SEO issue 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