wanderwithnicole.com website review

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

8 third-party services load with your homepage (loox.io, flodesk.com and Shopify and others), adding 1.2 MB and 476 ms of main-thread time.

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

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

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

flodesk.com costs a phone 100 ms of main-thread work and 588 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.

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

3 images could be 97 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 250 ms faster on a phone.

About 139 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

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

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

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

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

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

3 KiB could be saved by minifying CSS.

Your largest element takes 4.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “A collage of various images from a photography workshop in …”.

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

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

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 2.6 MB in 329 requests on a phone: other files 1.0 MB (192), images 666 KiB (27) and scripts 647 KiB (75). Under 2 MB keeps phones on slow connections fast.

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

Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.

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

Scrollable region must have keyboard access: 4 elements on the page fail this check, rated serious by axe-core.

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

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

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

Your <h1> is empty.

The homepage links to 42 pages on wanderwithnicole.com and 3 external pages.

There is no https://wanderwithnicole.com/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.

https://wanderwithnicole.com/policies/refund-policy has no meta description, so Google writes the search snippet from whatever text it finds.

https://wanderwithnicole.com/pages/hk-street-photography-course, https://wanderwithnicole.com/pages/hk-photography-workshop-teens, https://wanderwithnicole.com/pages/holiday-camp, https://wanderwithnicole.com/pages/corporate-team-building and https://wanderwithnicole.com/pages/family-photography have no <h1> headline, so visitors and search engines get no clear main topic.

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

3 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 “Access to XMLHttpRequest at 'https://data.stbuttons.click/data' from origin 'https://wanderwithnicole.com' has been blo…”.

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

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

Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (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 (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 35 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.