Website review, no card needed

shipblu.com logo

shipblu.com website review

Visit site (opens in a new tab)Reviewed 3 November 202640 issues · 80 checks

This review found 40 issues worth fixing on shipblu.com, 11 of them high impact, across 80 checks. The most urgent: use efficient cache lifetimes. 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
2.2 s1.8 sMay 16Oct 312.2 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.1 s
May 23, 20262.1 s
May 30, 20262.0 s
Jun 6, 20261.9 s
Jun 13, 20261.9 s
Jun 20, 20261.9 s
Jun 27, 20261.8 s
Jul 4, 20261.8 s
Jul 11, 20261.9 s
Jul 18, 20262.0 s
Jul 25, 20262.0 s
Aug 1, 20262.1 s
Aug 8, 20262.1 s
Aug 15, 20262.1 s
Aug 22, 20262.1 s
Aug 29, 20262.2 s
Sep 5, 20262.1 s
Sep 12, 20262.1 s
Sep 19, 20262.1 s
Sep 26, 20262.0 s
Oct 3, 20262.0 s
Oct 10, 20262.1 s
Oct 17, 20262.1 s
Oct 24, 20262.1 s
Oct 31, 20262.2 s
Real-visitor tap response (INP)75th percentile, phones
207 ms120 msMay 16Oct 31191 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026160 ms
May 23, 2026159 ms
May 30, 2026160 ms
Jun 6, 2026160 ms
Jun 13, 2026161 ms
Jun 20, 2026150 ms
Jun 27, 2026138 ms
Jul 4, 2026133 ms
Jul 11, 2026130 ms
Jul 18, 2026138 ms
Jul 25, 2026158 ms
Aug 1, 2026175 ms
Aug 8, 2026184 ms
Aug 15, 2026185 ms
Aug 22, 2026184 ms
Aug 29, 2026185 ms
Sep 5, 2026197 ms
Sep 12, 2026189 ms
Sep 19, 2026181 ms
Sep 26, 2026180 ms
Oct 3, 2026173 ms
Oct 10, 2026171 ms
Oct 17, 2026187 ms
Oct 24, 2026186 ms
Oct 31, 2026191 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 shipblu.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

5 to fix68
  • Use efficient cache lifetimes

    2.5 s · 3.5 MB

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

  • Reduce unused JavaScript

    2.3 s · 412 KiB

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

  • Mobile performance score: 68

    68/100

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

  • Render-blocking requests

    750 ms

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

  • ZenDesk adds 147 ms

    147 ms

    ZenDesk costs a phone 147 ms of main-thread work and 386 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.

  • 6 third-party services on the page

    6 third-party services load with your homepage (ZenDesk, Google Tag Manager and Clarity and others), adding 646 KiB and 277 ms of main-thread time.

  • 7 long tasks on the main thread

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

2 checks passed
  • Main-thread work: 1.4 s

    A phone's processor spends 1.4 s on main-thread work while loading, 448 ms of it running JavaScript. That is comfortably low.

  • Server response: 4 ms

    4 ms

    Your server sent the HTML in 4 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.

  • Largest Contentful Paint: 30.2 s

    30.2 s

    Your largest element takes 30.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Instant Payout Get Instant Access to Your Cash! Are you loo…”.

  • Time to Interactive: 32.3 s

    32.3 s

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

  • Real-user INP: 213 ms

    213 ms

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

  • Real-user FCP: 1.9 s

    1.9 s

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

  • 47 images without width and height

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

  • Speed Index: 4.2 s

    4.2 s

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

  • Total Blocking Time: 224 ms

    224 ms

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

  • First Contentful Paint: 1.8 s

    1.8 s

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

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

    +18%

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

  • Largest content (LCP) held steady for real visitors

    +2%

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

4 checks passed
  • Real-user LCP: 2.3 s

    2.3 s

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user TTFB: 606 ms

    606 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

4 to fix38
  • Page weight: 9.3 MB in 78 requests

    9.3 MB

    Your homepage downloads 9.3 MB in 78 requests on a phone: images 8.5 MB (52), scripts 731 KiB (8) and HTML 41 KiB (1). Under 2 MB keeps phones on slow connections fast.

  • 3 images over 500 KB

    3 images weigh 6.4 MB together. On a phone connection a single image that size takes seconds.

  • 19 images below the first screen load straight away

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

  • 4 images far larger than shown

    287 KiB

    4 images are downloaded at several times the size a phone draws them, for example 11.2488ac80.png at 1,920 px wide, shown at 74 px. Resized copies would save about 287 KiB.

  • 6 images in older formats

    6 images (428 KiB) 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.

  • About 2.6 g of CO₂ per visit

    2.64 g

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

Accessibility

6 to fixGoogle 7187
  • 3 text elements with low contrast

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

  • 45 images without alt text

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

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

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

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

  • 11 links without text

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

1 checks passed
  • 24 automated accessibility rules passed

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

SEO

7 to fixGoogle 7561
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No H1 headline

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

  • Title is short (17 characters)

    Your title is only 17 characters: “ShipBlu - ShipBlu”. 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.

  • No canonical URL

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

  • No social preview image

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

  • 2 links crawlers can't follow

    2 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 incomplete here.

  • 9 internal links, 17 external

    The homepage links to 9 pages on shipblu.com and 17 external pages.

2 checks passed
  • 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://shipblu.com/sitemap_index.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://shipblu.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 (504 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix85
  • 6 pages without a meta description

    https://shipblu.com/blog, https://shipblu.com/entrepreneurship/revenue-based-financing-a-game-changer-for-ecommerce-business-owners-in-egypt, https://shipblu.com/business-development/from-browsing-to-buying-how-bnpl-can-boost-your-online-sales, https://shipblu.com/ecommerce/hidden-shipping-secrets-how-lack-of-communication-can-derail-your-ecommerce-business, https://shipblu.com/ar/%d8%a7%d9%84%d8%b4%d8%b1%d9%88%d8%b7-%d9%88%d8%a7%d9%84%d8%a3%d8%ad%d9%83%d8%a7%d9%85 and https://shipblu.com/get-started-with-shipblu have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://shipblu.com/ar/%d8%a7%d9%84%d8%b4%d8%b1%d9%88%d8%b7-%d9%88%d8%a7%d9%84%d8%a3%d8%ad%d9%83%d8%a7%d9%85, whose canonical is https://shipblu.com/ar/%D8%A7%D9%84%D8%B4%D8%B1%D9%88%D8%B7-%D9%88%D8%A7%D9%84%D8%A3%D8%AD%D9%83%D8%A7%D9%85. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 4 pages without an H1

    https://shipblu.com/business-development/from-browsing-to-buying-how-bnpl-can-boost-your-online-sales, https://shipblu.com/ecommerce/hidden-shipping-secrets-how-lack-of-communication-can-derail-your-ecommerce-business, https://shipblu.com/privacy-policy and https://shipblu.com/get-started-with-shipblu have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://shipblu.com/ar/%d8%a7%d9%84%d8%b4%d8%b1%d9%88%d8%b7-%d9%88%d8%a7%d9%84%d8%a3%d8%ad%d9%83%d8%a7%d9%85 has 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.

  • 7 internal pages checked

    We fetched 7 pages linked from your homepage and read each the way a search engine does.

4 checks passed
  • Linked pages load

    All 7 pages we checked loaded without an error.

  • 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 7 pages that loaded have a <title>.

Best practices

Google 100100
3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix75
  • 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 phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • Thin social proof

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

  • No analytics detected

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

  • No opening hours

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

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • 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 494 words of copy

    The homepage carries about 494 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: “Start Shipping”.

  • 6 calls to action

    The homepage has 6 calls to action, for example “Start Shipping” and “Get Started”.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 1 email 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
  • 4 trackers load before any consent

    4

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

  • 5 cookies set on arrival

    5

    Opening the homepage sets 5 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.

  • 13 other companies contacted

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

Upkeep, stack and company

Stack

CMS
Gridsome v0.7.23
Framework
Vue.js

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 40 issues on shipblu.com, including 14 speed issues, 7 SEO issues and 4 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