makemejedi.com website review

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

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

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

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

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

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

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

8 third-party services load with your homepage (loox.io, omnisnippet1.com and emotivecdn.io and others), adding 1.4 MB and 2.0 s of main-thread time.

loox.io costs a phone 579 ms of main-thread work and 325 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.

omnisnippet1.com costs a phone 456 ms of main-thread work and 129 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.

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

emotivecdn.io costs a phone 210 ms of main-thread work and 384 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.

rebuyengine.com costs a phone 199 ms of main-thread work and 300 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.

Polyfills for old browsers add 74 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 50 ms faster on a phone.

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

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

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

5 KiB could be saved by minifying CSS.

Your largest element takes 40.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “HAND-DRAWN WITH CARE BY REAL ARTISTS Turn Your Loved ones i…”.

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

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

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

41 images have no width and height attributes, so the layout jumps as each one loads.

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 131 ms to 136 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.0 s to 2.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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 16.0 MB in 494 requests on a phone: images 10.9 MB (89), scripts 2.2 MB (84) and other files 2.1 MB (253). Under 2 MB keeps phones on slow connections fast.

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

9 images are downloaded at several times the size a phone draws them, for example Group_1597880456_1.png at 4,320 px wide, shown at 593 px. Resized copies would save about 4.6 MB.

15 images further down the page (7.9 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

image_252_1200x.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

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

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

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

Some list items are not inside a list.

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

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

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

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

Your title is 75 characters, so Google will cut it off around 60: “MakeMeJedi - Turn Your Loved Ones Into Star Wars Characters! – Make Me Jedi”.

There are 2 <h1> headlines (“” and “Turn Your Loved ones into Jedi”). One clear main headline is easier for people and search engines.

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

No Open Graph image, 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.

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

The homepage links to 130 pages on makemejedi.com and 4 external pages.

https://makemejedi.com/products/custom-make-me-jedi-framed-portrait, https://makemejedi.com/products/custom-make-me-jedi-portrait-unframed-poster, https://makemejedi.com/products/custom-make-me-jedi-portrait-mug, https://makemejedi.com/products/custom-make-me-jedi-portrait-blanket and https://makemejedi.com/products/custom-make-me-jedi-portrait-christmas-acrylic-ornament have no <h1> headline, so visitors and search engines get no clear main topic.

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

5 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 displayed at the wrong aspect ratio, so it looks stretched or squashed.

Requests the notification permission on page load.

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

The homepage carries about 1,119 words of visible text.

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