abscent.com website review

4 images could be 633 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.6 s faster on a phone.

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

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

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

8 third-party services load with your homepage (Hotjar, Clarity and Google Tag Manager and others), adding 765 KiB and 755 ms of main-thread time.

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

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

Shopify costs a phone 124 ms of main-thread work and 316 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.

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

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

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

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

4 KiB could be saved by minifying CSS.

3 KiB could be saved by minifying JavaScript.

Your largest element takes 15.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “At Abscent our mission is simple - provide our customers wi…”.

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

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

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

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

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

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 images are downloaded at several times the size a phone draws them, for example slide3.jpg at 1,920 px wide, shown at 351 px. Resized copies would save about 501 KiB.

Your homepage downloads 3.1 MB in 371 requests on a phone: scripts 1.0 MB (136), other files 1.0 MB (201) and images 824 KiB (12). Under 2 MB keeps phones on slow connections fast.

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

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

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

6 tap targets are too small or too close together to hit reliably with a finger.

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

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

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

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

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

Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.

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

Your title is 70 characters, so Google will cut it off around 60: “Abscent Smell Proof Bags- Backpacks, Duffle Bags, Toiletry Bags, Pouch”.

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

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

No XML sitemap at https://www.abscent.com/sitemap.xml, so Google discovers your pages only by following links.

Your <h1> is empty.

The homepage links to 80 pages on abscent.com and 7 external pages.

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.

There is no /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.

15 pages we tried to fetch timed out or refused automated requests, so these checks couldn't run. Some firewalls do this to every bot, including search engine crawlers they don't recognise.

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

5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

2 links go through two or more redirects, for example https://instagram.com/abscentdesign.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

abscent.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

abscent.com has no DMARC record, so nothing tells receivers what to do with mail that fails SPF or DKIM. Gmail and Yahoo require DMARC from bulk senders.

abscent.com has no SPF record, so mail servers can't tell which servers may send email as you. Your mail lands in spam more often, and anyone can send mail pretending to be you.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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

Opening the homepage sets 16 cookies (measured from a US location before any click).

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.

Loading the homepage contacts 38 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.