Website review, no card needed

newhaven-usa.com logo

newhaven-usa.com website review

Visit site (opens in a new tab)Reviewed 20 November 202640 issues · 93 checks

This review found 40 issues worth fixing on newhaven-usa.com, 18 of them high impact, across 93 checks. The most urgent: reduce unused JavaScript. 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.1 s1.6 sMay 30Nov 141.8 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.8 s
Jun 6, 20261.9 s
Jun 13, 20262.1 s
Jun 20, 20262.0 s
Jun 27, 20262.0 s
Jul 4, 20261.9 s
Jul 11, 20261.8 s
Jul 18, 20261.8 s
Jul 25, 20261.7 s
Aug 1, 20261.8 s
Aug 8, 20261.7 s
Aug 15, 20261.7 s
Aug 22, 20261.7 s
Aug 29, 20261.7 s
Sep 5, 20261.8 s
Sep 12, 20261.9 s
Sep 19, 20261.8 s
Sep 26, 20261.7 s
Oct 3, 20261.7 s
Oct 10, 20261.7 s
Oct 17, 20261.7 s
Oct 24, 20261.7 s
Oct 31, 20261.8 s
Nov 7, 20261.8 s
Nov 14, 20261.8 s
Real-visitor tap response (INP)75th percentile, phones
134 ms101 msMay 30Nov 14128 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026119 ms
Jun 6, 2026127 ms
Jun 13, 2026129 ms
Jun 20, 2026128 ms
Jun 27, 2026128 ms
Jul 4, 2026121 ms
Jul 11, 2026114 ms
Jul 18, 2026112 ms
Jul 25, 2026105 ms
Aug 1, 2026108 ms
Aug 8, 2026105 ms
Aug 15, 2026107 ms
Aug 22, 2026110 ms
Aug 29, 2026110 ms
Sep 5, 2026110 ms
Sep 12, 2026112 ms
Sep 19, 2026110 ms
Sep 26, 2026111 ms
Oct 3, 2026112 ms
Oct 10, 2026112 ms
Oct 17, 2026121 ms
Oct 24, 2026127 ms
Oct 31, 2026130 ms
Nov 7, 2026129 ms
Nov 14, 2026128 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 newhaven-usa.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. newhaven-usa.com at 1.2 s1.2 s
  2. newhaven-usa.com at 2.4 s2.4 s
  3. newhaven-usa.com at 3.6 s3.6 s
  4. newhaven-usa.com at 4.8 s4.8 s
  5. newhaven-usa.com at 6.0 s6.0 s
  6. newhaven-usa.com at 7.2 s7.2 s
  7. newhaven-usa.com at 8.4 s8.4 s
  8. newhaven-usa.com at 9.6 s9.6 s

Speed

13 to fix42
  • Reduce unused JavaScript

    25.0 s · 3.3 MB

    About 3.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 25.0 s faster on a phone.

  • Reduce unused CSS

    2.6 s · 232 KiB

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

  • YouTube adds 1.9 s

    1.9 s

    YouTube costs a phone 1.9 s of main-thread work and 5.1 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Use efficient cache lifetimes

    1.8 s · 371 KiB

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

  • Render-blocking requests

    1.4 s

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

  • Mobile performance score: 42

    42/100

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

  • Main-thread work: 8.3 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (YouTube, Google Tag Manager and Yotpo and others), adding 19.1 MB and 2.7 s of main-thread time.

  • Shopify adds 69 ms

    69 ms

    Shopify costs a phone 69 ms of main-thread work and 12.8 MB 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.

  • Legacy JavaScript

    300 ms · 48 KiB

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

  • Google Tag Manager adds 251 ms

    251 ms

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

  • 2,234 HTML elements

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

  • Klaviyo adds 110 ms

    110 ms

    Klaviyo costs a phone 110 ms of main-thread work and 311 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.

  • 20 long tasks on the main thread

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

  • Improve image delivery

    100 ms · 126 KiB

    10 images could be 126 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 100 ms faster on a phone.

  • Minify JavaScript

    150 ms · 43 KiB

    43 KiB could be saved by minifying JavaScript.

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

1 checks passed
  • Server response: 16 ms

    16 ms

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

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 55.4 s

    55.4 s

    Your largest element takes 55.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “NEW HAVEN HAS LANDED IN PENSACOLA. We are excited to be ope…”.

  • Speed Index: 21.3 s

    21.3 s

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

  • Time to Interactive: 60.7 s

    60.7 s

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

  • Total Blocking Time: 987 ms

    987 ms

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

  • 37 images without width and height

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

  • First Contentful Paint: 2.0 s

    2.0 s

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

  • Tap response (INP) held steady for real visitors

    +4%

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

  • Largest content (LCP) held steady for real visitors

    -5%

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

7 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 2.5 s

    2.5 s

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

  • Real-user INP: 154 ms

    154 ms

    Real visitors wait 154 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 FCP: 1.5 s

    1.5 s

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

  • Real-user TTFB: 598 ms

    598 ms

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

  • Cumulative Layout Shift: 0.033

    0.033

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

Images and page weight

2 to fix63
  • Page weight: 23.8 MB in 475 requests

    23.8 MB

    Your homepage downloads 23.8 MB in 475 requests on a phone: media 12.5 MB (1), scripts 6.2 MB (129) and images 1.6 MB (89). Under 2 MB keeps phones on slow connections fast.

  • 14 images below the first screen load straight away

    14 images further down the page (554 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 6.7 g of CO₂ per visit

    6.73 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

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

Accessibility

7 to fixGoogle 7889
  • 4 buttons without a name

    4 buttons have no accessible name, so screen readers announce just “button”.

  • 13 text elements with low contrast

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

  • Hidden but focusable

    3 elements hidden from screen readers can still receive keyboard focus.

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • 131 images without alt text

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

  • 42 links without text

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

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

1 checks passed
  • 50 automated accessibility rules passed

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

SEO

3 to fixGoogle 8586
  • Title is long (69 characters)

    Your title is 69 characters, so Google will cut it off around 60: “The Ultimate Moving and Storage Solution – New Haven Moving Equipment”.

  • 7 H1 headlines

    There are 7 <h1> headlines (“New Haven has landed in Pensacola.”, “Built for the Professional Mover” and “Professional Dollies”). One clear main headline is easier for people and search engines.

  • 13 links crawlers can't follow

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

  • 306 internal links, 12 external

    The homepage links to 306 pages on newhaven-usa.com and 12 external pages.

6 checks passed
  • Meta description: 155 characters

    Your meta description is 155 characters: “Your one-stop shop for moving and storage needs. 20 nationwide locations, serving since 1911. Check out our premium mov…”.

  • Canonical URL set

    The canonical URL is https://newhaven-usa.com/.

  • Structured data in place

    Structured data found: Organization 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://newhaven-usa.com/sitemap.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: 6 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://newhaven-usa.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90
  • 1 page without a meta description

    https://newhaven-usa.com/apps/store-locator has no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages without an H1

    https://newhaven-usa.com/pages/frequently-asked-questions, https://newhaven-usa.com/pages/resources, https://newhaven-usa.com/pages/get-in-touch and https://newhaven-usa.com/apps/store-locator have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

5 to fixGoogle 6969
  • 3 broken images

    3 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=97109680&Ver=2&mid=71bf1609-40e1-49c9-bd4f-5adc0c22621d&bo=1&sid=7c15bba0e51f11f1b2b3a9c9c7e581ed&vid=7c15ddf0e51f11f184cc2595b19d232c&vids=1&msclkid=N&pi=918639831&lg.

  • 17 small tap targets

    17 of 66 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.

  • 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 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

  • Browser-reported issues

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix94
  • 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 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,202 words of copy

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

8 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Register” and “Shop Moving Boxes”.

  • 48 calls to action

    The homepage has 48 calls to action, for example “Contact Us”, “Shop Moving Boxes” and “Shop Packaging”.

  • 32 short forms

    32 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 14 testimonial or review blocks, 1 customer or partner logo and 4 trust badges.

  • Analytics in place

    Analytics detected: Google Analytics and Microsoft Clarity.

  • Direct contact links

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

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

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

  • 32 cookies set on arrival

    32

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

  • 56 other companies contacted

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

Apps on your store

No apps were seen in the code your storefront loads.

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

E-commerce
Shopify
Hosting
Shopify

Company

Headquarters
San Fernando

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 newhaven-usa.com, including 19 speed issues, 3 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