Website review, no card needed

uniquemaps.eu logo

uniquemaps.eu website review

Visit site (opens in a new tab)Reviewed 20 November 202641 issues · 91 checks

This review found 41 issues worth fixing on uniquemaps.eu, 13 of them high impact, across 91 checks. The most urgent: page weight: 14.2 MB in 443 requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
3.6 s3.0 sMay 30Nov 143.4 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20263.4 s
Jun 6, 20263.3 s
Jun 13, 20263.4 s
Jun 20, 20263.4 s
Jun 27, 20263.4 s
Jul 4, 20263.5 s
Jul 11, 20263.5 s
Jul 18, 20263.4 s
Jul 25, 20263.3 s
Aug 1, 20263.1 s
Aug 8, 20263.1 s
Aug 15, 20263.1 s
Aug 22, 20263.2 s
Aug 29, 20263.2 s
Sep 5, 20263.2 s
Sep 12, 20263.2 s
Sep 19, 20263.4 s
Sep 26, 20263.4 s
Oct 3, 20263.5 s
Oct 10, 20263.4 s
Oct 17, 20263.5 s
Oct 24, 20263.5 s
Oct 31, 20263.4 s
Nov 7, 20263.6 s
Nov 14, 20263.4 s
Real-visitor tap response (INP)75th percentile, phones
392 ms238 msMay 30Nov 14319 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026256 ms
Jun 6, 2026273 ms
Jun 13, 2026305 ms
Jun 20, 2026316 ms
Jun 27, 2026342 ms
Jul 4, 2026364 ms
Jul 11, 2026355 ms
Jul 18, 2026356 ms
Jul 25, 2026316 ms
Aug 1, 2026287 ms
Aug 8, 2026311 ms
Aug 15, 2026304 ms
Aug 22, 2026337 ms
Aug 29, 2026374 ms
Sep 5, 2026359 ms
Sep 12, 2026367 ms
Sep 19, 2026342 ms
Sep 26, 2026291 ms
Oct 3, 2026277 ms
Oct 10, 2026260 ms
Oct 17, 2026271 ms
Oct 24, 2026293 ms
Oct 31, 2026298 ms
Nov 7, 2026320 ms
Nov 14, 2026319 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of uniquemaps.eu (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. uniquemaps.eu at 0.4 s0.4 s
  2. uniquemaps.eu at 0.8 s0.8 s
  3. uniquemaps.eu at 1.1 s1.1 s
  4. uniquemaps.eu at 1.5 s1.5 s
  5. uniquemaps.eu at 1.9 s1.9 s
  6. uniquemaps.eu at 2.3 s2.3 s
  7. uniquemaps.eu at 2.6 s2.6 s
  8. uniquemaps.eu at 3.0 s3.0 s

Speed

12 to fix65
  • Main-thread work: 5.3 s

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

  • 4,639 HTML elements

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

  • Improve image delivery

    8.2 MB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, commoninja.com and loox.io and others), adding 10.7 MB and 1.5 s of main-thread time.

  • commoninja.com adds 354 ms

    354 ms

    commoninja.com costs a phone 354 ms of main-thread work and 9.0 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.

  • Mobile performance score: 65

    65/100

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

  • Render-blocking requests

    950 ms

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

  • Reduce unused JavaScript

    851 KiB

    About 851 KiB of JavaScript is downloaded but never used on this page.

  • Google Tag Manager adds 521 ms

    521 ms

    Google Tag Manager costs a phone 521 ms of main-thread work and 687 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.

  • Use efficient cache lifetimes

    429 KiB

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

  • Reduce unused CSS

    300 ms · 67 KiB

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

  • loox.io adds 268 ms

    268 ms

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

  • 9 long tasks on the main thread

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

  • Minify CSS

    150 ms · 10 KiB

    10 KiB could be saved by minifying CSS.

  • Font display

    50 ms

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

  • Legacy JavaScript

    31 KiB

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

  • Chained critical requests

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

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

1 checks passed
  • Server response: 15 ms

    15 ms

    Your server sent the HTML in 15 ms, well inside Google's 600 ms guideline.

Core Web Vitals

9 to fix67
  • Fails Core Web Vitals for real visitors

    Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

  • Time to Interactive: 33.4 s

    33.4 s

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

  • Largest Contentful Paint: 5.8 s

    5.8 s

    Your largest element takes 5.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Find a map of a place that matters Antique maps, art prints…”.

  • Speed Index: 6.9 s

    6.9 s

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

  • Real-user CLS: 0.23

    0.23

    For real visitors the layout shifts by 0.23 (75th percentile). Good is under 0.1.

  • Tap response (INP) got 21% slower for real visitors

    +21%

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

  • Real-user TTFB: 810 ms

    810 ms

    Real visitors wait 810 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Total Blocking Time: 314 ms

    314 ms

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

  • 8 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    +4%

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

5 checks passed
  • Real-user LCP: 1.8 s

    1.8 s

    Real visitors wait 1.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 189 ms

    189 ms

    Real visitors wait 189 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user FCP: 1.7 s

    1.7 s

    Real visitors see the first content after 1.7 s (75th percentile). Good is under 1.8 s.

  • First Contentful Paint: 1.4 s

    1.4 s

    The first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

4 to fix28
  • Page weight: 14.2 MB in 443 requests

    14.2 MB

    Your homepage downloads 14.2 MB in 443 requests on a phone: images 9.8 MB (71), scripts 2.2 MB (84) and other files 1.5 MB (266). Under 2 MB keeps phones on slow connections fast.

  • 4 images far larger than shown

    1.2 MB

    4 images are downloaded at several times the size a phone draws them, for example MOD_3D_EdwardStanford1898highresnewaged_coloured_popartframe at 1,800 px wide, shown at 170 px. Resized copies would save about 1.2 MB.

  • 1 image over 500 KB

    MOD_3D_EdwardStanford1898highresnewaged_coloured_popartframe weighs 536 KiB. On a phone connection a single image that size takes seconds.

  • 4 images below the first screen load straight away

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

  • 1 image in older formats

    1 image (206 KiB) is 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.

  • About 4.0 g of CO₂ per visit

    4.02 g

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

Accessibility

5 to fixGoogle 8794
  • Hidden but focusable

    1 element hidden from screen readers can still receive keyboard focus.

  • 7 images without alt text

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

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 4 links without text

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

  • Alternative text of images should not be repeated as text (4 elements)

    Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

1 checks passed
  • 49 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 6 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

5 to fixGoogle 8577
  • Title is long (69 characters)

    Your title is 69 characters, so Google will cut it off around 60: “The Unique Maps Co. - Personalised & Vintage Old Map Shop - Est. 1984”.

  • 2 H1 headlines

    There are 2 <h1> headlines (“The Unique Maps Co.” and “Find a map of somewhere that mattersFind a map of…”). One clear main headline is easier for people and search engines.

  • Meta description is long (285 characters)

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

  • Structured data has 1 problem

    Structured data found (OnlineStore and Product) but with 1 problem, for example “Product: no offers (price) block”.

  • 1 link with vague text

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

  • 392 internal links, 12 external

    The homepage links to 392 pages on uniquemaps.eu and 12 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://uniquemaps.com/.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://uniquemaps.com/sitemap.xml.

AI search readiness

100
4 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • Text is in the HTML

    Your server sends the page's text in the HTML (5,294 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://uniquemaps.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

1 to fix95
  • 15 pages without an H1

    https://uniquemaps.com/collections/all-old-vintage-antique-maps, https://uniquemaps.com/collections/unique-3d-maps, https://uniquemaps.com/collections/ski-resort-maps-posters-piste-maps, https://uniquemaps.com/collections/custom-made-maps, https://uniquemaps.com/collections/newest-maps-added-to-the-unique-maps-co-collection and https://uniquemaps.com/collections/large-old-maps and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 3 pages with very little text

    https://uniquemaps.com/collections/old-military-and-battle-maps-illustrations, https://uniquemaps.com/collections/railway-maps-travel and https://uniquemaps.com/collections/old-maps-of-the-moon-star-charts 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.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9678
  • 10 broken images

    10 images failed to load on a phone, for example https://uniquemaps.com/?shpxid=f960c279-af9b-44af-bc8e-b6be04499d7f.

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_SOCKET_NOT_CONNECTED”.

2 checks passed
  • Tap targets are thumb-sized

    24 of 29 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • No call to action on the first screen

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

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • About 905 words of copy

    The homepage carries about 905 words of visible text.

7 checks passed
  • 7 calls to action

    The homepage has 7 calls to action, for example “Shop by style”, “Shop by artist” and “Call (818) 804-4732”.

  • 6 short forms

    6 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 513 testimonial or review blocks, 43 customer or partner logos, a star rating, 13 trust badges and “8,000+ reviews”.

  • Analytics in place

    Analytics detected: Microsoft Clarity.

  • Direct contact links

    Visitors can reach you directly: 4 phone links and 0 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 9 trackers load before any consent

    9

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

  • 26 cookies set on arrival

    26

    Opening the homepage sets 26 cookies, 2 of them by other companies (measured from a US location before any click).

  • No consent tool detected

    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.

  • 40 other companies contacted

    Loading the homepage contacts 40 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at uniquemaps.eu, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 15 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Simprosys Google Shopping Feed · Elevar Conversion Tracking · Doofinder Search Discovery · Klaviyo Email Marketing Sms · synctrack.io · loox.io · cloudfront.net · gorgias.chat · gelato.tech · hextom.com · omnisnippet1.com · hubapi.com · recomaticapp.com · 9gtb.com · Swym Wishlist Plus

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

E-commerce
Shopify
Analytics
Microsoft Clarity
Hosting
Shopify

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 41 issues on uniquemaps.eu, including 21 speed issues, 5 SEO issues and 2 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25