shoreprojects.com website review

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

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

4 images could be 1.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 700 ms faster on a phone.

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

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

About 87 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.

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

8 third-party services load with your homepage (Shopify, Yotpo and Facebook and others), adding 1,012 KiB and 254 ms of main-thread time.

11 KiB could be saved by minifying CSS.

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

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

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

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

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

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

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

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

Your homepage downloads 7.0 MB in 377 requests on a phone: images 4.6 MB (53), scripts 1.0 MB (147) and other files 868 KiB (143). Under 2 MB keeps phones on slow connections fast.

3 images weigh 3.5 MB together. On a phone connection a single image that size takes seconds.

2 images are downloaded at several times the size a phone draws them, for example shere.jpg at 3,000 px wide, shown at 390 px. Resized copies would save about 1.1 MB.

2 images (1.6 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

2 images further down the page (64 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.98 g of CO₂e: 237.0 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”.

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

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

All page content should be contained by landmarks: 21 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.

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

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

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

Elements with role="dialog" or role="alertdialog" do not have accessible names. (1 element).

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

ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.

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

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

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

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

1 link has no real href, so search engines can't follow it.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 24 pages on shoreprojects.com and 6 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.

https://www.shoreprojects.com/collections/all-watches, https://www.shoreprojects.com/blogs/news and https://www.shoreprojects.com/pages/faqs have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.shoreprojects.com/collections/all-watches, https://www.shoreprojects.com/collections/straps, https://www.shoreprojects.com/products/gift-card, https://www.shoreprojects.com/pages/about, https://www.shoreprojects.com/blogs/news and https://www.shoreprojects.com/collections/watches and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 11 pages linked from your homepage and read each the way a search engine does.

1 image failed to load on a phone, for example https://www.shoreprojects.com/cdn/shop/t/27/assets/WhiteShoreFlag_191195595fb808c789a15183aaae5e8d.png?v=13284.

2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

3 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 image is served at too low a resolution for sharp phone screens.

Chrome logged issues while loading the page (“Cookie”).

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

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

Opening the homepage sets 20 cookies, 2 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 43 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.