homer.com website review

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

Signyfyd costs a phone 1.5 s of main-thread work and 537 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

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

8 third-party services load with your homepage (Signyfyd, Google Tag Manager and Accessibe Accessibility Overlay and others), adding 1.9 MB and 2.4 s of main-thread time.

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

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

74 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 150 ms faster on a phone.

1 image could be 20 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

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

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

16 KiB could be saved by minifying JavaScript.

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 9.8 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 22.3 s. Good is under 3.8 s.

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

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

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

Your homepage downloads 5.9 MB in 522 requests on a phone: images 1.9 MB (57), scripts 1.8 MB (91) and other files 1.7 MB (354). Under 2 MB keeps phones on slow connections fast.

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

8 dropdowns have no label.

24 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 7 elements on the page fail this check, rated moderate by axe-core.

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

Elements with visible text labels do not have matching accessible names. (200 elements).

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is only 28 characters: “Homer - Official Online Shop”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

The homepage links to 117 pages on homer.com and 8 external pages.

/products/sodium-ring and /products/sodium-ring-silver all use the title “Sodium Ring | Silver Jewelry | Homer | Frank Ocean”. Search engines can't tell which page to show for a search, so each competes with the others.

/collections/sodium and /collections/beef-broccoli-life have no meta description, so Google writes the search snippet from whatever text it finds.

/products/sodium-bracelet and /products/sodium-bracelet-xl use the same meta description. A description written for each page earns more clicks.

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

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

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

1 error was logged to the browser console while the page loaded, for example “__SCRIPTLOADER__ ERROR MESSAGE: A profile is currently in flight. pageView() / reset() were called before the previous …”.

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

1 link go through two or more redirects, for example https://instagram.com/homer.

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.

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

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

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

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 2,905 words of visible text.

DMARC is set to p=none, so mail pretending to be homer.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 and Klaviyo (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 14 cookies, 1 of them by other companies (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 23 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.