Website review, no card needed

gotomorris.com logo

gotomorris.com website review

Visit site (opens in a new tab)Reviewed 3 November 202629 issues · 78 checks

This review found 29 issues worth fixing on gotomorris.com, 14 of them high impact, across 78 checks. The most urgent: render-blocking requests. 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.3 s1.6 sMay 16Oct 312.9 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.8 s
May 23, 20261.9 s
May 30, 20262.1 s
Jun 6, 20262.3 s
Jun 13, 20262.6 s
Jun 20, 20262.2 s
Jun 27, 20262.2 s
Jul 4, 20262.2 s
Jul 11, 20262.4 s
Jul 18, 20262.6 s
Jul 25, 20263.0 s
Aug 1, 20263.1 s
Aug 8, 20263.1 s
Aug 15, 20263.1 s
Aug 22, 20263.0 s
Aug 29, 20262.9 s
Sep 5, 20262.9 s
Sep 12, 20262.7 s
Sep 19, 20262.8 s
Sep 26, 20262.7 s
Oct 3, 20262.7 s
Oct 10, 20262.9 s
Oct 17, 20262.9 s
Oct 24, 20263.1 s
Oct 31, 20262.9 s
Real-visitor tap response (INP)75th percentile, phones
99 ms72 msMay 16Oct 3196 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202679 ms
May 23, 202685 ms
May 30, 202681 ms
Jun 6, 202687 ms
Jun 13, 202688 ms
Jun 20, 202686 ms
Jun 27, 202682 ms
Jul 4, 202676 ms
Jul 11, 202675 ms
Jul 18, 202679 ms
Jul 25, 202679 ms
Aug 1, 202686 ms
Aug 8, 202686 ms
Aug 15, 202682 ms
Aug 22, 202686 ms
Aug 29, 202681 ms
Sep 5, 202679 ms
Sep 12, 202679 ms
Sep 19, 202679 ms
Sep 26, 202679 ms
Oct 3, 202682 ms
Oct 10, 202690 ms
Oct 17, 202692 ms
Oct 24, 202696 ms
Oct 31, 202696 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 gotomorris.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. gotomorris.com at 0.4 s0.4 s
  2. gotomorris.com at 0.8 s0.8 s
  3. gotomorris.com at 1.3 s1.3 s
  4. gotomorris.com at 1.7 s1.7 s
  5. gotomorris.com at 2.1 s2.1 s
  6. gotomorris.com at 2.5 s2.5 s
  7. gotomorris.com at 3.0 s3.0 s
  8. gotomorris.com at 3.4 s3.4 s

Speed

8 to fix53
  • Render-blocking requests

    2.8 s

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

  • Reduce unused JavaScript

    1.8 s · 322 KiB

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

  • Use efficient cache lifetimes

    950 ms · 361 KiB

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

  • Mobile performance score: 53

    53/100

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

  • Reduce unused CSS

    700 ms · 96 KiB

    About 96 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 700 ms faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Hubspot and cptn.co and others), adding 913 KiB and 630 ms of main-thread time.

  • Google Tag Manager adds 275 ms

    275 ms

    Google Tag Manager costs a phone 275 ms of main-thread work and 509 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.

  • Main-thread work: 2.5 s

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

  • Legacy JavaScript

    250 ms · 34 KiB

    Polyfills for old browsers add 34 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 250 ms faster on a phone.

  • 12 long tasks on the main thread

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

  • Font display

    100 ms

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

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

  • Minify CSS

    3 KiB

    3 KiB could be saved by minifying CSS.

  • Minify JavaScript

    3 KiB

    3 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 15 ms

    15 ms

    Your server sent the HTML in 15 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: 19.4 s

    19.4 s

    Your largest element takes 19.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use cookies and similar technologies to support this web…”.

  • Time to Interactive: 20.1 s

    20.1 s

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

  • Speed Index: 6.9 s

    6.9 s

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

  • First Contentful Paint: 3.0 s

    3.0 s

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

  • Real-user LCP: 2.9 s

    2.9 s

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

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

    +61%

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

  • Real-user FCP: 2.4 s

    2.4 s

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

  • Total Blocking Time: 430 ms

    430 ms

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

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

    +17%

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

4 checks passed
  • Real-user INP: 96 ms

    96 ms

    Real visitors wait 96 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.

  • Real-user TTFB: 638 ms

    638 ms

    Real visitors wait 638 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 fix25
  • Page weight: 4.7 MB in 108 requests

    4.7 MB

    Your homepage downloads 4.7 MB in 108 requests on a phone: images 3.3 MB (20), scripts 909 KiB (39) and fonts 176 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    MTO_MTC_Standard-Automation_2025_Cobot_1920X1080.jpg weighs 745 KiB. On a phone connection a single image that size takes seconds.

  • 2 images far larger than shown

    632 KiB

    2 images are downloaded at several times the size a phone draws them, for example MTO_MTC_Standard-Automation_2025_Cobot_1920X1080.jpg at 2,048 px wide, shown at 308 px. Resized copies would save about 632 KiB.

  • 2 images in older formats

    2 images (954 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 1.3 g of CO₂ per visit

    1.32 g

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

1 checks passed
  • Images load when needed

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

Accessibility

3 to fixGoogle 9195
  • 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.

  • 3 tap targets too small

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

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

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

  • Headings skip levels

    Headings skip levels (h3 → h5), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 10 images in the HTML carry an alt attribute.

  • 43 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 4 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
  • 2 H1 headlines

    There are 2 <h1> headlines (“Put Us To Work.” and “CNC MACHINE TOOLS, AUTOMATION AND SUPPORT FOR MAN…”). One clear main headline is easier for people and search engines.

  • 65 internal links, 16 external

    The homepage links to 65 pages on gotomorris.com and 16 external pages.

7 checks passed
  • Meta description: 136 characters

    Your meta description is 136 characters: “Morris provides CNC machine tools, automation, applications engineering, service, parts, training, and financing for U.…”.

  • Title: 60 characters

    Your title is a healthy 60 characters: “CNC Machine Tool Distributor | Automation & Support | Morris”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, Organization, WebPage 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://www.gotomorris.com/sitemap_index.xml.

AI search readiness

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

  • llms.txt published

    The site publishes https://www.gotomorris.com/llms.txt (2 KiB, 29 links), a plain-text guide to the site for AI tools.

Other pages

100
  • 15 internal pages checked

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

7 checks passed
  • Linked pages load

    13 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 13 pages that loaded have a meta description.

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

Best practices

2 to fixGoogle 9687
  • 5 small tap targets

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

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix50
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • No social proof

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

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

  • About 611 words of copy

    The homepage carries about 611 words of visible text.

2 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Contact Morris” and “Sign Up Now”.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and HubSpot.

Privacy and tracking

  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and HubSpot (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

  • 12 cookies set on arrival

    12

    Opening the homepage sets 12 cookies (measured from a US location before any click).

  • 20 other companies contacted

    Loading the homepage contacts 20 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: HubSpot cookie banner

    A consent management tool (HubSpot cookie banner) loads with the page.

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 gotomorris.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 | Google Tag Manager
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 29 issues on gotomorris.com, including 17 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