Website review, no card needed

marcothepolo.com logo

marcothepolo.com website review

Visit site (opens in a new tab)Reviewed 9 November 202630 issues · 85 checks

This review found 30 issues worth fixing on marcothepolo.com, 10 of them high impact, across 85 checks. The most urgent: reduce unused JavaScript. 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.9 s2.2 sMay 23Jul 183.1 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20262.8 s
May 30, 20262.6 s
Jun 6, 20262.6 s
Jun 13, 20262.5 s
Jun 20, 20262.4 s
Jun 27, 20263.1 s
Jul 4, 20263.7 s
Jul 11, 20263.7 s
Jul 18, 20263.1 s
Real-visitor tap response (INP)75th percentile, phones
252 ms194 msMay 23Jul 4201 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026234 ms
May 30, 2026231 ms
Jun 6, 2026245 ms
Jun 13, 2026220 ms
Jun 20, 2026227 ms
Jun 27, 2026215 ms
Jul 4, 2026201 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 marcothepolo.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. marcothepolo.com at 0.4 s0.4 s
  2. marcothepolo.com at 0.9 s0.9 s
  3. marcothepolo.com at 1.3 s1.3 s
  4. marcothepolo.com at 1.7 s1.7 s
  5. marcothepolo.com at 2.2 s2.2 s
  6. marcothepolo.com at 2.6 s2.6 s
  7. marcothepolo.com at 3.0 s3.0 s
  8. marcothepolo.com at 3.5 s3.5 s

Speed

7 to fix66
  • Reduce unused JavaScript

    1.8 s · 676 KiB

    About 676 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.8 s faster on a phone.

  • Render-blocking requests

    1.9 s

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

  • Reduce unused CSS

    1.4 s · 217 KiB

    About 217 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.4 s faster on a phone.

  • Main-thread work: 4.1 s

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

  • 3,221 HTML elements

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

  • Mobile performance score: 66

    66/100

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

  • Shopify adds 72 ms

    72 ms

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Clarity, Shopify and reddit and others), adding 755 KiB and 267 ms of main-thread time.

  • 4 long tasks on the main thread

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

  • Improve image delivery

    118 KiB

    5 images could be 118 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Use efficient cache lifetimes

    82 KiB

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

  • Font display

    50 ms

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

  • Minify JavaScript

    19 KiB

    19 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    11 KiB

    Polyfills for old browsers add 11 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: 9 ms

    9 ms

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

Core Web Vitals

5 to fix58
  • Largest Contentful Paint: 11.3 s

    11.3 s

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

  • Time to Interactive: 11.6 s

    11.6 s

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

  • Largest content (LCP) got 26% slower for real visitors

    +26%

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

  • Speed Index: 4.4 s

    4.4 s

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

  • Cumulative Layout Shift: 0.137

    0.137

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

  • Not enough real-visitor data yet

    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.

3 checks passed
  • Tap response (INP) got 11% faster for real visitors

    -11%

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

  • Total Blocking Time: 147 ms

    147 ms

    Scripts block the page for only 147 ms while loading. Good is under 200 ms.

  • First Contentful Paint: 1.1 s

    1.1 s

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

Images and page weight

1 to fix85
  • Page weight: 3.0 MB in 249 requests

    3.0 MB

    Your homepage downloads 3.0 MB in 249 requests on a phone: scripts 1.1 MB (61), other files 837 KiB (121) and images 595 KiB (45). Under 2 MB keeps phones on slow connections fast.

  • About 0.8 g of CO₂ per visit

    0.84 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

7 to fixGoogle 8891
  • 70 tap targets too small

    70 tap targets are too small or too close together to hit reliably with a finger.

  • 22 text elements with low contrast

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

  • All page content should be contained by landmarks (16 elements)

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

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 6 form fields without a label

    6 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • 4 links without text

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

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h1 → h3), 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).

2 checks passed
  • Every image has alt text

    All 24 images in the HTML carry an alt attribute.

  • 40 automated accessibility rules passed

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

SEO

1 to fixGoogle 10095
  • Meta description is long (185 characters)

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

  • 260 internal links, 6 external

    The homepage links to 260 pages on marcothepolo.com and 6 external pages.

7 checks passed
  • One H1 headline

    Your main headline reads: “MarcoThePolo”.

  • Title: 64 characters

    Your title is a healthy 64 characters: “MarcoThePolo - Buy Wholesale Products Online Shopping from China”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, ClothingStore and WebSite.

  • 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://marcothepolo.com/sitemap.xml.

AI search readiness

1 to fix88
  • No Organization structured data

    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.

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

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

2 to fix90
  • 14 pages without a meta description

    https://marcothepolo.com/collections/new-arrival-jewelry-accessories, https://marcothepolo.com/collections/new-arrival-mens-clothing, https://marcothepolo.com/collections/new-arrival-1, https://marcothepolo.com/collections/new-arrival-kids, https://marcothepolo.com/collections/new-arrival-bags and https://marcothepolo.com/collections/new-arrival-shoes and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 pages without an H1

    https://marcothepolo.com/pages/fresh-new-arrival, https://marcothepolo.com/collections/new-arrival-jewelry-accessories, https://marcothepolo.com/collections/new-arrival-mens-clothing, https://marcothepolo.com/collections/new-arrival-1, https://marcothepolo.com/collections/new-arrival-kids and https://marcothepolo.com/collections/new-arrival-bags and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

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

  • 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

3 to fixGoogle 9276
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=187080668&tm=shpfy_ui&Ver=2&mid=5c9d77cd-37cf-4621-af2b-7f854526d0f8&bo=1&sid=32d38040dc8c11f1aefe21b551ffbf0d&vid=32d383e0dc8c11f1bbe8716581dea992&vids=1&msclkid=N&pi.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Uncaught ReferenceError: OK is not defined”.

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix88
  • 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.

  • Thin social proof

    Social proof on the homepage: 7 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

  • About 763 words of copy

    The homepage carries about 763 words of visible text.

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP NOW”.

  • 12 calls to action

    The homepage has 12 calls to action, for example “Beauty Skin Care Makeup Shop”, “SHOP NOW” and “SHOP NOW->”.

  • 4 short forms

    4 short forms (2 fields at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Microsoft Clarity.

  • Direct contact links

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

  • Phone number on the homepage

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

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

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

  • 12 cookies set on arrival

    12

    Opening the homepage sets 12 cookies (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.

  • 30 other companies contacted

    Loading the homepage contacts 30 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 marcothepolo.com, 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 8 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Cbb Keep Share Cart · Jekka Intelligent Ai Chatbot · shareasale.com · stamped.io · cart-bot.net · intercom.io · quickcep.com · aliyuncs.com

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

Framework
jQuery
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 30 issues on marcothepolo.com, including 12 speed issues, 1 SEO issue 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