idoido-weddingfavors.com website review

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

42 files are served with short cache lifetimes, so returning visitors download them again (7.8 MB).

12 images could be 4.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

5 third-party services load with your homepage (Google Tag Manager, Symantec and Bootstrap CDN and others), adding 489 KiB and 207 ms of main-thread time.

About 21 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.

2 KiB could be saved by minifying CSS.

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

The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

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

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

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

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

Your largest element takes 4.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “For wedding gifts and favors, choose IdoIdo-Wedding Favors …”. Most of its time is element render delay (4.3 s).

1 image 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 8.2 MB in 56 requests on a phone: images 7.6 MB (33), scripts 492 KiB (11) and fonts 76 KiB (1). Under 2 MB keeps phones on slow connections fast.

4 images weigh 5.5 MB together. On a phone connection a single image that size takes seconds.

8 images are downloaded at several times the size a phone draws them, for example IMG_0230.jpg at 3,525 px wide, shown at 135 px. Resized copies would save about 3.9 MB.

13 images (6.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.

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

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

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

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

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

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

Your title is 81 characters, so Google will cut it off around 60: “Wedding Favors | Wedding Gifts | Wedding Guest Book | Baby Shower | Bridal Favors”.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

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

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

4 links have no real href, so search engines can't follow them.

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

The homepage links to 142 pages on idoido-weddingfavors.com and 2 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.idoido-weddingfavors.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://www.idoido-weddingfavors.com/Mall.php, https://www.idoido-weddingfavors.com/products/tiffany-cutlery-set-w-chopsticks, https://www.idoido-weddingfavors.com/products/eco-friendly-bamboo-dinner-cutlery-, https://www.idoido-weddingfavors.com/products/ceramic-handle-cutlery-set-fork-and-spoon, https://www.idoido-weddingfavors.com/products/elegant-tiara-place-card-holder and https://www.idoido-weddingfavors.com/products/rainbow-jello-towel and 6 others have no <title>, so Google invents the link text in results.

https://www.idoido-weddingfavors.com/Mall.php, https://www.idoido-weddingfavors.com/products/tiffany-cutlery-set-w-chopsticks, https://www.idoido-weddingfavors.com/products/eco-friendly-bamboo-dinner-cutlery-, https://www.idoido-weddingfavors.com/products/ceramic-handle-cutlery-set-fork-and-spoon, https://www.idoido-weddingfavors.com/products/elegant-tiara-place-card-holder and https://www.idoido-weddingfavors.com/products/rainbow-jello-towel and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.idoido-weddingfavors.com/products/tiffany-cutlery-set-w-chopsticks took over 3 s to send its HTML from our server.

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

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

13 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

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.

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

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