Website review, no card needed

abbottnyc.com logo

abbottnyc.com website review

Visit site (opens in a new tab)Reviewed 20 October 202638 issues · 83 checks

This review found 38 issues worth fixing on abbottnyc.com, 11 of them high impact, across 83 checks. The most urgent: use efficient cache lifetimes. 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.5 sMay 16Oct 171.8 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.8 s
May 23, 20261.8 s
May 30, 20261.9 s
Jun 6, 20261.8 s
Jun 13, 20261.8 s
Jun 20, 20261.9 s
Jun 27, 20261.7 s
Jul 4, 20261.6 s
Jul 11, 20261.8 s
Jul 18, 20261.9 s
Jul 25, 20262.0 s
Aug 1, 20262.1 s
Aug 22, 20261.9 s
Oct 10, 20261.8 s
Oct 17, 20261.8 s
Real-visitor tap response (INP)75th percentile, phones
105 ms73 msMay 2Oct 1783 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 202685 ms
May 16, 202696 ms
May 23, 2026101 ms
May 30, 202698 ms
Jun 6, 202695 ms
Jun 13, 202687 ms
Jun 20, 202686 ms
Jun 27, 202687 ms
Jul 4, 202680 ms
Jul 11, 202687 ms
Jul 18, 202687 ms
Jul 25, 202686 ms
Aug 1, 202696 ms
Aug 8, 202695 ms
Aug 22, 202696 ms
Aug 29, 202692 ms
Oct 3, 202687 ms
Oct 10, 202677 ms
Oct 17, 202683 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 abbottnyc.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. abbottnyc.com at 0.7 s0.7 s
  2. abbottnyc.com at 1.4 s1.4 s
  3. abbottnyc.com at 2.2 s2.2 s
  4. abbottnyc.com at 2.9 s2.9 s
  5. abbottnyc.com at 3.6 s3.6 s
  6. abbottnyc.com at 4.3 s4.3 s
  7. abbottnyc.com at 5.0 s5.0 s
  8. abbottnyc.com at 5.7 s5.7 s

Speed

11 to fix52
  • Use efficient cache lifetimes

    6.2 s · 994 KiB

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

  • Reduce unused JavaScript

    2.8 s · 699 KiB

    About 699 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.8 s faster on a phone.

  • Render-blocking requests

    1.9 s

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

  • Reduce unused CSS

    1.1 s · 199 KiB

    About 199 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (alia-prod.com, route.com and Facebook and others), adding 1.5 MB and 868 ms of main-thread time.

  • Mobile performance score: 52

    52/100

    Your mobile performance score is 52 (desktop: 81). Pages that score under 90 lose visitors before the first paint.

  • Legacy JavaScript

    300 ms · 48 KiB

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

  • Improve image delivery

    295 KiB

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

  • 6 long tasks on the main thread

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

  • route.com adds 211 ms

    211 ms

    route.com costs a phone 211 ms of main-thread work and 566 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.

  • Main-thread work: 2.1 s

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

  • Font display

    50 ms

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

  • Phones get a much slower page than desktops

    Desktop scores 81 but mobile only 52. A gap that wide usually means heavy scripts and images that hit phones hardest.

  • Minify CSS

    7 KiB

    7 KiB could be saved by minifying CSS.

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

1 checks passed
  • Server response: 4 ms

    4 ms

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

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 18.4 s

    18.4 s

    Your largest element takes 18.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “DISCOVER PAPAYA ISLA PERFUME SHOP NOW”.

  • Time to Interactive: 19.5 s

    19.5 s

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

  • First Contentful Paint: 5.7 s

    5.7 s

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

  • Speed Index: 7.0 s

    7.0 s

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

  • Total Blocking Time: 303 ms

    303 ms

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

  • 10 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    -1%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.8 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.8 s

    1.8 s

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

  • Real-user INP: 83 ms

    83 ms

    Real visitors wait 83 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.6 s

    1.6 s

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

  • Real-user TTFB: 417 ms

    417 ms

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

  • Tap response (INP) got 12% faster for real visitors

    -12%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 85 ms to 83 ms 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).

Images and page weight

2 to fix75
  • Page weight: 3.7 MB in 243 requests

    3.7 MB

    Your homepage downloads 3.7 MB in 243 requests on a phone: scripts 1.7 MB (72), other files 811 KiB (129) and images 719 KiB (21). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    22 KiB

    1 image is downloaded at several times the size a phone draws it, for example 190920_ABBOTT_33451.jpg at 1,365 px wide, shown at 390 px. Resized copies would save about 22 KiB.

  • 3 images below the first screen load straight away

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

  • About 1.0 g of CO₂ per visit

    1.05 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.05 g of CO₂e: 125.4 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 8188
  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

  • 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 (7 elements)

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

  • Zoom is disabled

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

  • 3 form fields without a label

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

  • 3 links without text

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

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

1 checks passed
  • 32 automated accessibility rules passed

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

SEO

3 to fixGoogle 9284
  • Title is short (16 characters)

    Your title is only 16 characters: “Abbott Fragrance”. 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.

  • Meta description is short (56 characters)

    Your meta description is only 56 characters: “unisex clean fragrances inspired by natural destinations”. 70 to 160 characters is enough to sell the click.

  • 46 internal links, 14 external

    The homepage links to 46 pages on abbottnyc.com and 14 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “DISCOVER PAPAYA ISLA PERFUME”.

  • Canonical URL set

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

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

  • llms.txt published

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

Other pages

2 to fix90
  • 3 pages without a meta description

    https://abbottnyc.com/pages/pura, https://abbottnyc.com/pages/our-story and https://abbottnyc.com/pages/fragrance-inspired-by-sequoia have no meta description, so Google writes the search snippet from whatever text it finds.

  • 7 pages without an H1

    https://abbottnyc.com/collections/shop-all, https://abbottnyc.com/collections/perfumes, https://abbottnyc.com/collections/candles, https://abbottnyc.com/pages/pura, https://abbottnyc.com/collections/shop-gifts and https://abbottnyc.com/pages/our-story and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

  • 4 pages with very little text

    https://abbottnyc.com/collections/candles, https://abbottnyc.com/collections/shop-gifts, https://abbottnyc.com/pages/contact and https://abbottnyc.com/pages/fragrance-inspired-by-sequoia 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.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 18 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

3 to fixGoogle 9671
  • 1 broken image

    1 image failed to load on a phone, for example https://lantern.roeye.com/track.php?fingerprint=c06696db-eadd-49f5-91d4-2dc4c2f7367a&referrer=&landingpage=https%3A%2F%2Fabbottnyc.com%2F&useragent=Mozilla%2F5.0%20(iPhone%3B%20CPU%20iPhone%20OS%2017_.

  • 6 small tap targets

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

  • 4 JavaScript errors while loading

    4 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 ()”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix86
  • Thin social proof

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

  • Only about 178 words

    The homepage has only about 178 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.

5 checks passed
  • Clear next step on the first screen

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

  • 10 calls to action

    The homepage has 10 calls to action, for example “Shop”, “Register” and “Contact”.

  • 1 short form

    A short form (1 field at most) is right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Meta Pixel.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 1 email link.

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

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

  • 14 cookies set on arrival

    14

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

  • 35 other companies contacted

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

Upkeep, stack and company

Stack

Framework
jQuery
E-commerce
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 38 issues on abbottnyc.com, including 17 speed issues, 3 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