Website review, no card needed

mitsumidistribution.com logo

mitsumidistribution.com website review

Visit site (opens in a new tab)Reviewed 4 November 202630 issues · 50 checks

This review found 30 issues worth fixing on mitsumidistribution.com, 13 of them high impact, across 50 checks. The most urgent: avoid multiple page redirects. 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
5.4 s3.8 sMay 16Oct 314.0 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20264.5 s
May 23, 20264.3 s
May 30, 20264.3 s
Jun 6, 20264.2 s
Jun 13, 20264.2 s
Jun 20, 20264.4 s
Jun 27, 20264.4 s
Jul 4, 20264.2 s
Jul 11, 20264.4 s
Jul 18, 20264.4 s
Jul 25, 20264.4 s
Aug 1, 20265.2 s
Aug 8, 20264.4 s
Aug 15, 20264.4 s
Oct 24, 20264.1 s
Oct 31, 20264.0 s

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 mitsumidistribution.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. mitsumidistribution.com at 0.9 s0.9 s
  2. mitsumidistribution.com at 1.8 s1.8 s
  3. mitsumidistribution.com at 2.7 s2.7 s
  4. mitsumidistribution.com at 3.6 s3.6 s
  5. mitsumidistribution.com at 4.5 s4.5 s
  6. mitsumidistribution.com at 5.4 s5.4 s
  7. mitsumidistribution.com at 6.3 s6.3 s
  8. mitsumidistribution.com at 7.2 s7.2 s

Speed

7 to fix63
  • Avoid multiple page redirects

    15.8 s

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

  • Use efficient cache lifetimes

    10.0 s · 2.0 MB

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

  • Reduce unused JavaScript

    9.8 s · 888 KiB

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

  • Reduce unused CSS

    1.8 s · 143 KiB

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

  • Improve image delivery

    1.4 s · 261 KiB

    2 images could be 261 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.4 s faster on a phone.

  • Mobile performance score: 63

    63/100

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

  • Main-thread work: 2.1 s

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

  • 5 long tasks on the main thread

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

  • 2 third-party services on the page

    2 third-party services load with your homepage (Google Tag Manager and Google Fonts), adding 197 KiB and 42 ms of main-thread time.

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

1 checks passed
  • Server response: 1 ms

    1 ms

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

Core Web Vitals

8 to fix0
  • 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.

  • Real-user CLS: 0.33

    0.33

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

  • Largest Contentful Paint: 25.2 s

    25.2 s

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

  • Time to Interactive: 25.2 s

    25.2 s

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

  • Speed Index: 9.7 s

    9.7 s

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

  • Real-user LCP: 4.0 s

    4.0 s

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

  • Real-user TTFB: 960 ms

    960 ms

    Real visitors wait 960 ms for your server to start answering (75th percentile). Good is under 800 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.

  • Largest content (LCP) held steady for real visitors

    -7%

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

3 checks passed
  • Real-user FCP: 1.4 s

    1.4 s

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

  • Cumulative Layout Shift: 0.074

    0.074

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

  • Total Blocking Time: 66 ms

    66 ms

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

Images and page weight

1 to fix50
  • Page weight: 3.7 MB in 103 requests

    3.7 MB

    Your homepage downloads 3.7 MB in 103 requests on a phone: scripts 2.7 MB (61), images 538 KiB (12) and stylesheets 268 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • About 1.0 g of CO₂ per visit

    1.04 g

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

Accessibility

1 to fix93
  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • No main landmark

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

SEO

6 to fixGoogle 10070
  • No H1 headline

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

  • Title is long (69 characters)

    Your title is 69 characters, so Google will cut it off around 60: “MitsumiDistribution - Accelerating Technology Adoption Across Markets”.

  • No canonical URL

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

  • Structured data has 1 problem

    Structured data found (Organization) but with 1 problem, for example “Organization: url points at a different host (https://mitsdev.deerak.com/)”.

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

  • Only 0 internal links

    The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

3 checks passed
  • Meta description: 125 characters

    Your meta description is 125 characters: “At Mitsumi Distribution, we deliver cutting-edge technology solutions that empower businesses to thrive in a connected …”.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

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

AI search readiness

1 to fix83
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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

Best practices

2 to fixGoogle 8888
  • 4 distorted images

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

  • 2 console errors

    2 errors were logged to the browser console during Google's test (“Error fetching footer APIs [object P]”).

  • 1 low-resolution image

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix40
  • No calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • Only about 0 words

    The homepage has only about 0 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No form on the homepage

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

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

1 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

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 mitsumidistribution.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 | Google Tag Manager
Hosting
Google Cloud

Company

Headquarters
Dubai

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 mitsumidistribution.com, including 15 speed issues, 6 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