Website review, no card needed

adessohome.com logo

adessohome.com website review

Visit site (opens in a new tab)Reviewed 19 October 202652 issues · 88 checks

This review found 52 issues worth fixing on adessohome.com, 18 of them high impact, across 88 checks. The most urgent: improve image delivery. 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
3.1 s2.2 sJun 20Oct 102.8 s
Show as table
DateReal-visitor load time (LCP)
Jun 20, 20263.0 s
Jun 27, 20262.9 s
Jul 4, 20262.7 s
Jul 11, 20262.6 s
Jul 18, 20262.5 s
Jul 25, 20262.4 s
Aug 1, 20262.3 s
Aug 8, 20262.3 s
Aug 15, 20262.3 s
Aug 22, 20262.4 s
Aug 29, 20262.4 s
Sep 5, 20262.8 s
Sep 12, 20262.9 s
Sep 19, 20262.9 s
Sep 26, 20263.0 s
Oct 3, 20262.9 s
Oct 10, 20262.8 s
Real-visitor tap response (INP)75th percentile, phones
82 ms58 msJun 27Oct 1079 ms
Show as table
DateReal-visitor tap response (INP)
Jun 27, 202671 ms
Jul 4, 202663 ms
Jul 11, 202666 ms
Aug 1, 202670 ms
Aug 8, 202671 ms
Aug 15, 202670 ms
Aug 29, 202663 ms
Sep 5, 202661 ms
Sep 12, 202663 ms
Sep 19, 202670 ms
Sep 26, 202671 ms
Oct 3, 202673 ms
Oct 10, 202679 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 adessohome.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. adessohome.com at 0.4 s0.4 s
  2. adessohome.com at 0.8 s0.8 s
  3. adessohome.com at 1.2 s1.2 s
  4. adessohome.com at 1.6 s1.6 s
  5. adessohome.com at 1.9 s1.9 s
  6. adessohome.com at 2.3 s2.3 s
  7. adessohome.com at 2.7 s2.7 s
  8. adessohome.com at 3.1 s3.1 s

Speed

12 to fix32
  • Improve image delivery

    14.7 s · 3.5 MB

    13 images could be 3.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 14.7 s faster on a phone.

  • Reduce unused JavaScript

    4.5 s · 1.3 MB

    About 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.5 s faster on a phone.

  • Use efficient cache lifetimes

    1.6 s · 574 KiB

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

  • Render-blocking requests

    1.3 s

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

  • Mobile performance score: 32

    32/100

    Your mobile performance score is 32 (desktop: 22). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google CDN, Google Tag Manager and Other Google APIs/SDKs and others), adding 8.1 MB and 1.3 s of main-thread time.

  • Reduce unused CSS

    900 ms · 117 KiB

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

  • Google CDN adds 821 ms

    821 ms

    Google CDN costs a phone 821 ms of main-thread work and 1.9 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.

  • cloudfront.net adds 0 ms

    0 ms

    cloudfront.net costs a phone 0 ms of main-thread work and 5.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.

  • Main-thread work: 3.5 s

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

  • Google Tag Manager adds 245 ms

    245 ms

    Google Tag Manager costs a phone 245 ms of main-thread work and 474 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.

  • Cloudflare CDN adds 55 ms

    55 ms

    Cloudflare CDN costs a phone 55 ms of main-thread work and 334 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.

  • Minify JavaScript

    150 ms · 40 KiB

    40 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    150 ms · 34 KiB

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

  • 19 long tasks on the main thread

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

  • Font display

    50 ms

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

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

  • Minify CSS

    3 KiB

    3 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 25 ms

    25 ms

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

Core Web Vitals

11 to fix0
  • 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: 27.2 s

    27.2 s

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

  • Time to Interactive: 27.2 s

    27.2 s

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

  • First Contentful Paint: 4.4 s

    4.4 s

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

  • Speed Index: 7.9 s

    7.9 s

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

  • Total Blocking Time: 627 ms

    627 ms

    Scripts block taps and scrolling for 627 ms in total while the page loads. Good is under 200 ms.

  • Real-user LCP: 2.6 s

    2.6 s

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

  • Real-user CLS: 0.22

    0.22

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

  • Real-user FCP: 1.9 s

    1.9 s

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

  • Cumulative Layout Shift: 0.221

    0.221

    The layout shifts by 0.221 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • 14 images without width and height

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

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

    +13%

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

  • Largest content (LCP) held steady for real visitors

    -2%

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

Images and page weight

5 to fix18
  • Page weight: 9.4 MB in 84 requests

    9.4 MB

    Your homepage downloads 9.4 MB in 84 requests on a phone: images 5.3 MB (32), scripts 2.8 MB (22) and other files 709 KiB (9). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    3395-01_fitz vignette3.jpg weighs 2.7 MB. On a phone connection a single image that size takes seconds.

  • 4 images far larger than shown

    2.7 MB

    4 images are downloaded at several times the size a phone draws them, for example 3395-01_fitz vignette3.jpg at 2,800 px wide, shown at 220 px. Resized copies would save about 2.7 MB.

  • 12 images in older formats

    12 images (3.4 MB) 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.

  • 8 images below the first screen load straight away

    8 images further down the page (524 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 2.7 g of CO₂ per visit

    2.67 g

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

Accessibility

7 to fixGoogle 7690
  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • 11 images without alt text

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

  • All page content should be contained by landmarks (7 elements)

    All page content should be contained by landmarks: 7 elements on the page fail this check, rated moderate by axe-core.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • 11 links without text

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

  • 2 form fields without a label

    2 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Users should be able to zoom and scale the text up to 500% (1 element)

    Users should be able to zoom and scale the text up to 500%: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h1 → h4), which makes the page harder to scan with a screen reader.

1 checks passed
  • 37 automated accessibility rules passed

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

SEO

6 to fixGoogle 8574
  • Title is short (13 characters)

    Your title is only 13 characters: “Home | Adesso”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

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

  • 2 H1 headlines

    There are 2 <h1> headlines (“Top Categories” and “Our Family Brands:”). One clear main headline is easier for people and search engines.

  • Meta description is long (180 characters)

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

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 72 internal links, 6 external

    The homepage links to 72 pages on adessohome.com and 6 external pages.

3 checks passed
  • Canonical URL set

    The canonical URL is https://adessohome.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://adessohome.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.

  • No llms.txt

    There is no https://adessohome.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

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

Other pages

4 to fix55
  • 1 linked page is broken

    Your homepage links to https://adessohome.com/Catalogs, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 1 linked page hidden from search

    https://adessohome.com/pc_combined_results.asp is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 2 pages share a title

    / and https://adessohome.com/pc_combined_results.asp all use the title “Home | Adesso”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 9 pages without an H1

    https://adessohome.com/pc_combined_results.asp, https://adessohome.com/Shop-Adesso, https://adessohome.com/Shop-ADS360, https://adessohome.com/Shop-Kooduu, https://adessohome.com/Shop-Simplee-Adesso and https://adessohome.com/Candle-Warming-Lamps and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 8 pages with very little text

    https://adessohome.com/Shop-Adesso, https://adessohome.com/Shop-ADS360, https://adessohome.com/Shop-Kooduu, https://adessohome.com/Shop-Simplee-Adesso, https://adessohome.com/Candle-Warming-Lamps and https://adessohome.com/Ceiling-Lamps and 2 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 8 pages slow to respond

    https://adessohome.com/pc_combined_results.asp, https://adessohome.com/Shop-ADS360, https://adessohome.com/Shop-Kooduu, https://adessohome.com/Shop-Simplee-Adesso, https://adessohome.com/Candle-Warming-Lamps and https://adessohome.com/Ceiling-Lamps and 2 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

3 checks passed
  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 9 pages that loaded have a meta description.

  • Every page has a title

    All 9 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9686
  • Scrolls sideways on phones

    On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Cannot set properties of undefined (setting 'ETADate')”.

2 checks passed
  • Tap targets are thumb-sized

    11 of 12 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix67
  • 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.

  • Thin social proof

    Social proof on the homepage: 3 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 394 words of copy

    The homepage carries about 394 words of visible text.

3 checks passed
  • 3 calls to action

    The homepage has 3 calls to action, for example “Shop”, “Shop Candle Warmers” and “Contact Us”.

  • 1 short form

    A short form (2 fields at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Cloudflare Web Analytics.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 6 cookies set on arrival

    6

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

  • 12 other companies contacted

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

Upkeep, stack and company

Stack

Analytics
Google Analytics | Google Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 52 issues on adessohome.com, including 23 speed issues, 6 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