Website review, no card needed

moveoneinc.com logo

moveoneinc.com website review

Visit site (opens in a new tab)Reviewed 29 October 202631 issues · 81 checks

This review found 31 issues worth fixing on moveoneinc.com, 14 of them high impact, across 81 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
2.6 s1.6 sMay 9Oct 241.7 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.1 s
May 16, 20262.0 s
May 23, 20261.9 s
May 30, 20262.1 s
Jun 6, 20261.9 s
Jun 13, 20262.2 s
Jun 20, 20262.1 s
Jun 27, 20262.2 s
Jul 4, 20262.4 s
Jul 11, 20262.3 s
Jul 18, 20262.4 s
Jul 25, 20262.5 s
Aug 1, 20262.3 s
Aug 8, 20262.4 s
Aug 15, 20262.2 s
Aug 22, 20262.0 s
Aug 29, 20261.9 s
Sep 5, 20261.8 s
Sep 12, 20261.8 s
Sep 19, 20262.1 s
Sep 26, 20262.1 s
Oct 3, 20262.0 s
Oct 10, 20261.8 s
Oct 17, 20261.7 s
Oct 24, 20261.7 s
Real-visitor tap response (INP)75th percentile, phones
91 ms73 msMay 9Oct 2475 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202676 ms
May 16, 202675 ms
May 23, 202678 ms
May 30, 202675 ms
Jun 6, 202680 ms
Jun 13, 202686 ms
Jun 20, 202682 ms
Jun 27, 202680 ms
Jul 4, 202688 ms
Jul 11, 202683 ms
Jul 18, 202685 ms
Jul 25, 202689 ms
Aug 1, 202681 ms
Aug 8, 202678 ms
Aug 15, 202676 ms
Aug 22, 202676 ms
Aug 29, 202677 ms
Sep 5, 202678 ms
Sep 12, 202678 ms
Sep 19, 202678 ms
Sep 26, 202680 ms
Oct 3, 202682 ms
Oct 10, 202678 ms
Oct 17, 202676 ms
Oct 24, 202675 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 moveoneinc.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

6 to fix60
  • Avoid multiple page redirects

    20.0 s

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

  • Improve image delivery

    2.2 s · 947 KiB

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

  • Reduce unused JavaScript

    2.5 s · 328 KiB

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

  • Render-blocking requests

    1.1 s

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

  • Mobile performance score: 60

    60/100

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

  • Font display

    350 ms

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

  • 5 long tasks on the main thread

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

  • 4 third-party services on the page

    4 third-party services load with your homepage (Other Google APIs/SDKs, Google Fonts and Cloudflare and others), adding 444 KiB and 19 ms of main-thread time.

  • Use efficient cache lifetimes

    45 KiB

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

  • Minify CSS

    10 ms · 8 KiB

    8 KiB could be saved by minifying CSS.

  • Legacy JavaScript

    10 KiB

    Polyfills for old browsers add 10 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.

2 checks passed
  • Main-thread work: 1.1 s

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

  • Server response: 101 ms

    101 ms

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

Core Web Vitals

8 to fix100
  • 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: 25.1 s

    25.1 s

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

  • Time to Interactive: 25.9 s

    25.9 s

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

  • First Contentful Paint: 6.3 s

    6.3 s

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

  • Speed Index: 6.3 s

    6.3 s

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

  • Real-user FCP: 2.2 s

    2.2 s

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

  • Real-user TTFB: 1.1 s

    1.1 s

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

  • 7 images without width and height

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

  • Tap response (INP) held steady for real visitors

    0%

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

6 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 INP: 89 ms

    89 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Largest content (LCP) got 15% faster for real visitors

    -15%

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

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 41 ms

    41 ms

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

Images and page weight

3 to fix53
  • Page weight: 5.9 MB in 164 requests

    5.9 MB

    Your homepage downloads 5.9 MB in 164 requests on a phone: images 4.5 MB (36), scripts 815 KiB (58) and fonts 409 KiB (14). Under 2 MB keeps phones on slow connections fast.

  • 13 images in older formats

    13 images (2.2 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.

  • 11 images below the first screen load straight away

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

  • About 1.7 g of CO₂ per visit

    1.68 g

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

1 checks passed
  • Images are sized for phones

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

Accessibility

5 to fixGoogle 8992
  • Unlabelled dropdowns

    1 dropdown has no label.

  • 59 text elements with low contrast

    59 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 (13 elements)

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

  • 2 form fields without a label

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 15 images in the HTML carry an alt attribute.

  • 39 automated accessibility rules passed

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

SEO

5 to fixGoogle 8573
  • No meta description

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

  • Title is short (20 characters)

    Your title is only 20 characters: “Home Page - Move One”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 4 H1 headlines

    There are 4 <h1> headlines (“60 +”, “80 +” and “1000 +”). One clear main headline is easier for people and search engines.

  • No social preview image

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

  • 6 links with vague text

    6 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 49 internal links, 9 external

    The homepage links to 49 pages on moveoneinc.com and 9 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://www.moveoneinc.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization, WebPage and WebSite.

  • 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://www.moveoneinc.com/sitemap_index.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.moveoneinc.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.

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.

  • Organization data: 4 of 6 facts

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

  • Text is in the HTML

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

Other pages

1 to fix95
  • 10 pages without a meta description

    https://www.moveoneinc.com/contact-us, https://www.moveoneinc.com/about-us, https://www.moveoneinc.com/international-moving, https://www.moveoneinc.com/government-logistics, https://www.moveoneinc.com/aid-and-relief and https://www.moveoneinc.com/international-courier and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 11 internal pages checked

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

6 checks passed
  • Linked pages load

    All 11 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.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 11 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://accounts.google.com/gsi/style' from origin 'https://www.moveoneinc.com' has been b…”.

  • 1 low-resolution image

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

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix83
  • 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 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,494 words of copy

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

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Contact us” and “CONTACT”.

  • 9 calls to action

    The homepage has 9 calls to action, for example “Contact us”, “Contact” and “Learn more”.

  • 1 short form

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

  • Analytics in place

    Analytics detected: Google Analytics and Cloudflare Web Analytics.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

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

  • 3 cookies set on arrival

    3

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

  • 6 other companies contacted

    Loading the homepage contacts 6 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 moveoneinc.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
WordPress
Framework
jQuery
Analytics
Google Analytics
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 31 issues on moveoneinc.com, including 14 speed issues, 5 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