Website review, no card needed

teamone-usa.com logo

teamone-usa.com website review

Visit site (opens in a new tab)Reviewed 29 October 202633 issues · 69 checks

This review found 33 issues worth fixing on teamone-usa.com, 17 of them high impact, across 69 checks. The most urgent: improve image delivery. 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

Full-page screenshot of teamone-usa.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. teamone-usa.com at 0.8 s0.8 s
  2. teamone-usa.com at 1.6 s1.6 s
  3. teamone-usa.com at 2.4 s2.4 s
  4. teamone-usa.com at 3.2 s3.2 s
  5. teamone-usa.com at 4.0 s4.0 s
  6. teamone-usa.com at 4.8 s4.8 s
  7. teamone-usa.com at 5.5 s5.5 s
  8. teamone-usa.com at 6.3 s6.3 s

Speed

12 to fix8
  • Improve image delivery

    2.5 s · 15.4 MB

    19 images could be 15.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.5 s faster on a phone.

  • Reduce unused JavaScript

    5.3 s · 989 KiB

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

  • Render-blocking requests

    3.3 s

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

  • Mobile performance score: 8

    8/100

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

  • Main-thread work: 4.6 s

    A phone's processor spends 4.6 s on main-thread work while loading, 1.9 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 (Squarespace, Google Tag Manager and Optanon and others), adding 2.3 MB and 2.1 s of main-thread time.

  • Squarespace adds 955 ms

    955 ms

    Squarespace costs a phone 955 ms of main-thread work and 1.3 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.

  • Reduce unused CSS

    910 ms · 157 KiB

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

  • Google Tag Manager adds 741 ms

    741 ms

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

  • Use efficient cache lifetimes

    500 ms · 110 KiB

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

  • Legacy JavaScript

    450 ms · 109 KiB

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

  • 20 long tasks on the main thread

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

  • 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: 36 ms

    36 ms

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

Core Web Vitals

7 to fix8
  • Largest Contentful Paint: 22.5 s

    22.5 s

    Your largest element takes 22.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “The Art of Speed: Metabo HPT Goes Full Speed Metal”.

  • Time to Interactive: 23.8 s

    23.8 s

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

  • First Contentful Paint: 6.4 s

    6.4 s

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

  • Speed Index: 10.7 s

    10.7 s

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

  • Cumulative Layout Shift: 0.603

    0.603

    The layout shifts by 0.603 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Total Blocking Time: 1.4 s

    1.4 s

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

  • 1 image without width and height

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Images and page weight

4 to fix28
  • Page weight: 19.2 MB in 132 requests

    19.2 MB

    Your homepage downloads 19.2 MB in 132 requests on a phone: images 16.5 MB (29), scripts 2.1 MB (55) and other files 250 KiB (27). Under 2 MB keeps phones on slow connections fast.

  • 18 images far larger than shown

    15.1 MB

    18 images are downloaded at several times the size a phone draws them, for example 050426_SURF_THUMB_UPDATED.webp at 1,920 px wide, shown at 164 px. Resized copies would save about 15.1 MB.

  • 10 images over 500 KB

    10 images weigh 14.5 MB together. On a phone connection a single image that size takes seconds.

  • 15 images below the first screen load straight away

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

  • About 5.4 g of CO₂ per visit

    5.44 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

Google 100100
  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed
  • Every image has alt text

    All 5 images in the HTML carry an alt attribute.

  • 42 automated accessibility rules passed

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

SEO

3 to fixGoogle 10081
  • No H1 headline

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

  • Meta description is long (166 characters)

    Your meta description is 166 characters; Google truncates after about 160, so the end of your pitch is cut.

  • Structured data has 1 problem

    Structured data found (WebSite) but with 1 problem, for example “WebSite: image is not an absolute URL ("//images.squarespace-cdn.com/content/v1/69722a8df0f32c00ec6…”.

  • 17 internal links, 4 external

    The homepage links to 17 pages on teamone-usa.com and 4 external pages.

5 checks passed
  • Title: 32 characters

    Your title is a healthy 32 characters: “Team One | The Aspiration Agency”.

  • Canonical URL set

    The canonical URL is https://www.teamone-usa.com/.

  • 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.teamone-usa.com/sitemap.xml.

AI search readiness

2 to fix63
  • Most text only appears after JavaScript runs

    17%

    A phone browser shows 282 words, but the HTML your server sends has only 49. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

  • 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://www.teamone-usa.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.

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.

Other pages

3 to fix83
  • 2 linked pages hidden from search

    https://www.teamone-usa.com/privacy-notice and https://www.teamone-usa.com/cookie-notice are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 2 pages without a meta description

    https://www.teamone-usa.com/privacy-notice and https://www.teamone-usa.com/cookie-notice have no meta description, so Google writes the search snippet from whatever text it finds.

  • 6 pages without an H1

    https://www.teamone-usa.com/expertise, https://www.teamone-usa.com/our-team, https://www.teamone-usa.com/culture, https://www.teamone-usa.com/contact, https://www.teamone-usa.com/privacy-notice and https://www.teamone-usa.com/cookie-notice have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://www.teamone-usa.com/our-team 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.

  • 6 internal pages checked

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

4 checks passed
  • Linked pages load

    All 6 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 a title

    All 6 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10093
  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://static1.squarespace.com/static/versioned-site-css/69722a8df0f32c00ec6825d0/746/5c5…”.

2 checks passed
  • Tap targets are thumb-sized

    17 of 18 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix80
  • 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 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 282 words of copy

    The homepage carries about 282 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: “Shop”.

  • 5 calls to action

    The homepage has 5 calls to action, for example “Contact Us” and “Contact”.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Direct contact links

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

Privacy and tracking

  • 3 trackers load before any consent

    3

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

  • 8 cookies set on arrival

    8

    Opening the homepage sets 8 cookies, 1 of them by other companies (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: OneTrust

    A consent management tool (OneTrust) 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 teamone-usa.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
Squarespace
Framework
jQuery
Analytics
Google Analytics | Google Tag Manager
Hosting
Squarespace

Company

Founded
1987
Headquarters
Los Angeles

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on teamone-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