Website review, no card needed

merebe-shop.com logo

merebe-shop.com website review

Visit site (opens in a new tab)Reviewed 17 November 202652 issues · 91 checks

This review found 52 issues worth fixing on merebe-shop.com, 18 of them high impact, across 91 checks. The most urgent: improve image delivery. 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

Full-page screenshot of merebe-shop.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. merebe-shop.com at 1.6 s1.6 s
  2. merebe-shop.com at 3.2 s3.2 s
  3. merebe-shop.com at 4.8 s4.8 s
  4. merebe-shop.com at 6.4 s6.4 s
  5. merebe-shop.com at 8.0 s8.0 s
  6. merebe-shop.com at 9.6 s9.6 s
  7. merebe-shop.com at 11.2 s11.2 s
  8. merebe-shop.com at 12.8 s12.8 s

Speed

13 to fix36
  • Improve image delivery

    6.5 s · 18.7 MB

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

  • Reduce unused JavaScript

    2.9 s · 826 KiB

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

  • Mobile performance score: 36

    36/100

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

  • Use efficient cache lifetimes

    350 ms · 3.8 MB

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

  • Font display

    850 ms

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

  • Avoid multiple page redirects

    780 ms

    The page goes through 1 redirect before it starts loading, costing about 780 ms. Link and advertise the final URL directly.

  • Document request latency

    750 ms

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

  • Render-blocking requests

    750 ms

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (YouTube, poxo.com and notifly.tech and others), adding 1.2 MB and 538 ms of main-thread time.

  • YouTube adds 480 ms

    480 ms

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

  • Reduce unused CSS

    300 ms · 132 KiB

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

  • Main-thread work: 3.4 s

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

  • 2,736 HTML elements

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

  • Minify JavaScript

    170 KiB

    170 KiB could be saved by minifying JavaScript.

  • 7 long tasks on the main thread

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

  • Legacy JavaScript

    6 KiB

    Polyfills for old browsers add 6 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: 254 ms

    254 ms

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

Core Web Vitals

6 to fix42
  • First Contentful Paint: 8.1 s

    8.1 s

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

  • Largest Contentful Paint: 20.6 s

    20.6 s

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

  • Speed Index: 17.3 s

    17.3 s

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

  • Time to Interactive: 25.8 s

    25.8 s

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

  • Cumulative Layout Shift: 0.34

    0.34

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

  • 125 images without width and height

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

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

1 checks passed
  • Total Blocking Time: 176 ms

    176 ms

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

Images and page weight

5 to fix18
  • Page weight: 24.9 MB in 132 requests

    24.9 MB

    Your homepage downloads 24.9 MB in 132 requests on a phone: images 22.7 MB (81), scripts 1.8 MB (17) and fonts 169 KiB (2). Under 2 MB keeps phones on slow connections fast.

  • 11 images far larger than shown

    1.6 MB

    11 images are downloaded at several times the size a phone draws them, for example Mobile Logo.jpg at 500 px wide, shown at 150 px. Resized copies would save about 1.6 MB.

  • 1 image over 500 KB

    Mobile Logo.jpg weighs 582 KiB. On a phone connection a single image that size takes seconds.

  • 24 images in older formats

    24 images (4.3 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.

  • 17 images below the first screen load straight away

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

  • About 7.1 g of CO₂ per visit

    7.06 g

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

Accessibility

9 to fixGoogle 5484
  • 66 text elements with low contrast

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

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • 59 images without alt text

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

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

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Zoom is disabled

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

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

  • 22 links without text

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

  • 3 form fields without a label

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

  • Headings skip levels

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

1 checks passed
  • 28 automated accessibility rules passed

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

SEO

4 to fixGoogle 8577
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is short (29 characters)

    Your title is only 29 characters: “Merebe l Premium Baby Clothes”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

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

  • 32 links crawlers can't follow

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

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 197 internal links, 23 external

    The homepage links to 197 pages on merebe-shop.com and 23 external pages.

5 checks passed
  • Meta description: 148 characters

    Your meta description is 148 characters: “Shop Baby clothes for your lovely little ones from newborn to 36 months l House Clothes, bodysuit, Coverall, Sleep Vest…”.

  • Canonical URL set

    The canonical URL is https://merebe-shop.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.

  • XML sitemap found

    Your XML sitemap is reachable at https://merebe-shop.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.

  • No llms.txt

    There is no https://merebe-shop.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.

2 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 (2,463 words), so crawlers that don't run JavaScript still read it.

Other pages

6 to fix62
  • 1 page without a title

    https://merebe-shop.com/myshop/board_list.html has no <title>, so Google invents the link text in results.

  • 10 pages share a title

    /, https://merebe-shop.com/link/bookmark.html, https://merebe-shop.com/link/shortcut.html, https://merebe-shop.com/myshop/index.html, https://merebe-shop.com/myshop/mileage/historyList.html and https://merebe-shop.com/myshop/coupon/coupon.html and 4 others all use the title “Merebe l Premium Baby Clothes”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages without a meta description

    https://merebe-shop.com/myshop/board_list.html and https://merebe-shop.com/board/consult/write.html have no meta description, so Google writes the search snippet from whatever text it finds.

  • 9 pages share a meta description

    https://merebe-shop.com/link/bookmark.html, https://merebe-shop.com/link/shortcut.html, https://merebe-shop.com/myshop/index.html, https://merebe-shop.com/myshop/mileage/historyList.html, https://merebe-shop.com/myshop/coupon/coupon.html and https://merebe-shop.com/board/index.html and 3 others use the same meta description. A description written for each page earns more clicks.

  • 2 links to non-canonical URLs

    Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://merebe-shop.com/board/free/list.html, whose canonical is https://merebe-shop.com/board/general-discussion-forum2/1002. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 11 pages without an H1

    https://merebe-shop.com/myshop/index.html, https://merebe-shop.com/myshop/mileage/historyList.html, https://merebe-shop.com/myshop/coupon/coupon.html, https://merebe-shop.com/myshop/board_list.html, https://merebe-shop.com/board/index.html and https://merebe-shop.com/board/free/list.html and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 3 pages with very little text

    https://merebe-shop.com/link/bookmark.html, https://merebe-shop.com/link/shortcut.html and https://merebe-shop.com/board/consult/write.html 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.

  • 5 pages slow to respond

    https://merebe-shop.com/link/shortcut.html, https://merebe-shop.com/myshop/index.html, https://merebe-shop.com/myshop/mileage/historyList.html, https://merebe-shop.com/board/consult/write.html and https://merebe-shop.com/product/list.html took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

2 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

Best practices

6 to fixGoogle 6545
  • No mobile viewport

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

  • 2 broken images

    2 images failed to load on a phone, for example https://m.merebe-shop.com/.

  • 22 small tap targets

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

  • 5 third-party cookies

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

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'USD')”.

  • 32 distorted images

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

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

  • Missing source maps

    Large scripts ship without source maps.

Content and conversion

1 to fix90
  • Thin social proof

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

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • 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 1,240 words of copy

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

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “JOIN US” and “My shop”.

  • 7 calls to action

    The homepage has 7 calls to action, for example “JOIN +3000 P”, “MY SHOP” and “Order History”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads 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.

  • 16 cookies set on arrival

    16

    Opening the homepage sets 16 cookies, 1 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.

  • 12 other companies contacted

    Loading the homepage contacts 12 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 merebe-shop.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Analytics
Google Analytics
Hosting
Korea Telecom

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 52 issues on merebe-shop.com, including 19 speed issues, 4 SEO issues and 1 conversion gap. 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