winnieandhuy.com website review

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

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

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

8 third-party services load with your homepage (Tumblr, YouTube and Google/Doubleclick Ads and others), adding 7.1 MB and 1.3 s of main-thread time.

Tumblr costs a phone 740 ms of main-thread work and 5.6 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.

YouTube costs a phone 414 ms of main-thread work and 1.1 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.

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

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

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

11 long tasks block the main thread while loading, the longest for 95 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).

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 files are served with short cache lifetimes, so returning visitors download them again (4 KiB).

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

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

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

The layout shifts by 0.385 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

2 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.1 MB in 97 requests on a phone: images 3.9 MB (27), scripts 2.7 MB (31) and HTML 137 KiB (18). Under 2 MB keeps phones on slow connections fast.

2 images weigh 1.2 MB together. On a phone connection a single image that size takes seconds.

7 images are downloaded at several times the size a phone draws them, for example tumblr_p47dtixyoe1skqnhmo1_1280.jpg at 1,280 px wide, shown at 390 px. Resized copies would save about 513 KiB.

7 images (3.0 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.

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

14 frames have no title, so screen-reader users cannot tell what they contain.

<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

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

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 18 characters: “Winnie Marries Huy”. Between 30 and 65 characters leaves room to say what you do and for whom.

Open Graph is missing og:description, so shared links fall back to guesses.

The homepage links to 23 pages on winnieandhuy.com and 3 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.

There is no https://www.winnieandhuy.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.

robots.txt blocks ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

/, https://www.winnieandhuy.com/post/185264513100, https://www.winnieandhuy.com/post/173461671670, https://www.winnieandhuy.com/post/170641153945 and https://www.winnieandhuy.com/page/2 all use the title “Winnie Marries Huy”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.winnieandhuy.com/welcome, https://www.winnieandhuy.com/venue, https://www.winnieandhuy.com/accommodations, https://www.winnieandhuy.com/post/185264513100, https://www.winnieandhuy.com/post/182595773830/happy-lunar-new-year and https://www.winnieandhuy.com/post/178088655745/celebrating-four-years-of-marriage and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.winnieandhuy.com/welcome, whose canonical is https://www.winnieandhuy.com/post/83440113689/hello. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.winnieandhuy.com/archive has no <h1> headline, so visitors and search engines get no clear main topic.

https://www.winnieandhuy.com/welcome, https://www.winnieandhuy.com/venue, https://www.winnieandhuy.com/post/185264513100, https://www.winnieandhuy.com/post/182595773830/happy-lunar-new-year, https://www.winnieandhuy.com/post/178088655745/celebrating-four-years-of-marriage and https://www.winnieandhuy.com/post/173461671670 and 8 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

No viewport meta tag, so phones render the desktop layout zoomed out.

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

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

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.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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.

The homepage has only about 147 words of visible text; thin pages give Google and first-time buyers little to go on.

There is no form on the homepage, so every lead has to click through to another page first.

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 Comscore and Google Ads (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 1 cookie, 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 16 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.