aspiga.com website review

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

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

The page has 11,639 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

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

8 third-party services load with your homepage (Shopify, Clarity and Facebook and others), adding 2.2 MB and 920 ms of main-thread time.

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

104 KiB could be saved by minifying JavaScript.

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

LoyaltyLion costs a phone 38 ms of main-thread work and 338 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.

About 104 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.

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

10 KiB could be saved by minifying CSS.

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

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

Polyfills for old browsers add 47 KiB JavaScript that modern phones do not need.

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

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.

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

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

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

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

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

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

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

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

Your homepage downloads 5.5 MB in 466 requests on a phone: scripts 3.1 MB (161), other files 1.3 MB (221) and fonts 425 KiB (8). Under 2 MB keeps phones on slow connections fast.

2 images further down the page (45 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 1.55 g of CO₂e: 186.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

3 buttons have no accessible name, so screen readers announce just “button”.

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

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

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

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

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

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

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

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

2 links have no real href, so search engines can't follow them.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 401 pages on aspiga.com and 23 external pages.

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

10 images failed to load on a phone, for example https://aspiga-uk.myshopify.com/cdn/shop/files/Wishlist.svg.

4 errors were logged to the browser console while the page loaded, for example “Access to fetch at 'https://eastsideintel.io/api/pixel/collect' from origin 'null' has been blocked by CORS policy: Res…”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

Large scripts ship without source maps.

1 link to other sites is dead, for example https://aspiga.pagetiger.com/bbfrawd/1 (404).

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

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.

aspiga.com is registered until Nov 2026. If it lapses, the site and its email stop working and someone else can buy the name. Renew it, and turn on auto-renew.

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

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

Your longest form asks for 8 fields (0 required). Every extra field lowers completion.

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

The homepage carries about 667 words of visible text.

DMARC is set to p=none, so mail pretending to be aspiga.com is still delivered. Add a report address, check the reports, then move to quarantine.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

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, Klaviyo and Meta Pixel and 4 mores (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

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

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