awesomeartifact.com website review

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

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

About 517 KiB of JavaScript is downloaded but never used on this page.

6 files block the first paint until they finish downloading. Deferring or inlining them could save about 500 ms.

8 third-party services load with your homepage (Shopify, Cloudflare CDN and Webkul and others), adding 1.3 MB and 346 ms of main-thread time.

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

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

Webkul costs a phone 31 ms of main-thread work and 342 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 42 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.

151 KiB could be saved by minifying JavaScript.

1 long task block the main thread while loading, the longest for 56 ms. During a long task the page ignores taps.

8 KiB JavaScript is shipped twice across bundles.

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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

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

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

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

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

Your homepage downloads 2.8 MB in 213 requests on a phone: scripts 1.2 MB (128), other files 836 KiB (53) and images 555 KiB (15). Under 2 MB keeps phones on slow connections fast.

aa-stories-michael-jordan-signing.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

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

4 elements hidden from screen readers can still receive keyboard focus.

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

1 visible link has no text or label, so screen readers cannot say where it goes.

Elements marked as presentational should be consistently ignored: 5 elements on the page fail this check, rated minor by axe-core.

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

Structured data found (ItemList, Organization and WebSite) but with 1 problem, for example “ItemList: itemListElement is an empty list”.

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

The homepage links to 192 pages on awesomeartifact.com and 3 external pages.

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.

/collections/creme-de-la-creme and /collections/baseball-balls use the same meta description. A description written for each page earns more clicks.

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

1 image failed to load on a phone, for example https://awesomeartifact.com/.

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

Requests the notification permission on page load.

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.

awesomeartifact.com is registered until Dec 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.

awesomeartifact.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

awesomeartifact.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 homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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 818 words of visible text.

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

DMARC is set to p=none, so mail pretending to be awesomeartifact.com is still delivered. Reports are on, so moving to quarantine is the next step.

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 Tag Manager, Meta Pixel and Pinterest Tag (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 8 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 15 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.