Website review, no card needed

averityteam.com logo

averityteam.com website review

Visit site (opens in a new tab)Reviewed 14 November 202631 issues · 79 checks

This review found 31 issues worth fixing on averityteam.com, 14 of them high impact, across 79 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

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

How it loaded on a phone

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

Speed

8 to fix54
  • Reduce unused JavaScript

    6.0 s · 1.2 MB

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

  • Improve image delivery

    1.6 s · 824 KiB

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

  • Render-blocking requests

    1.4 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google CDN, Google Tag Manager and Other Google APIs/SDKs and others), adding 2.2 MB and 866 ms of main-thread time.

  • Mobile performance score: 54

    54/100

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

  • Google CDN adds 579 ms

    579 ms

    Google CDN costs a phone 579 ms of main-thread work and 1.5 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

    450 ms · 84 KiB

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

  • Main-thread work: 2.6 s

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

  • Minify JavaScript

    120 ms · 18 KiB

    18 KiB could be saved by minifying JavaScript.

  • 14 long tasks on the main thread

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

  • Use efficient cache lifetimes

    81 KiB

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

  • Font display

    50 ms

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

  • Duplicated JavaScript

    10 KiB

    10 KiB JavaScript is shipped twice across bundles.

  • Legacy JavaScript

    6 KiB

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

  • Minify CSS

    4 KiB

    4 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 4 ms

    4 ms

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

Core Web Vitals

4 to fix64
  • First Contentful Paint: 9.9 s

    9.9 s

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

  • Largest Contentful Paint: 21.5 s

    21.5 s

    Your largest element takes 21.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Human by Averity”.

  • Time to Interactive: 24.5 s

    24.5 s

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

  • Speed Index: 9.9 s

    9.9 s

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

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

2 checks passed
  • Total Blocking Time: 179 ms

    179 ms

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

  • Cumulative Layout Shift: 0.025

    0.025

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

Images and page weight

1 to fix70
  • Page weight: 14.4 MB in 108 requests

    14.4 MB

    Your homepage downloads 14.4 MB in 108 requests on a phone: media 8.8 MB (1), images 2.0 MB (13) and scripts 2.0 MB (44). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

    1 image (30 KiB) is 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 4.1 g of CO₂ per visit

    4.09 g

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

2 checks passed
  • Images load when needed

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

  • Images are sized for phones

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

Accessibility

10 to fixGoogle 8588
  • 9 text elements with low contrast

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

  • 7 tap targets too small

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

  • Form elements should have a visible label (4 elements)

    Form elements should have a visible label: 4 elements on the page fail this check, rated serious by axe-core.

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

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

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

  • Document should not have more than one banner landmark (1 element)

    Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • 11 form fields without a label

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

  • 6 links without text

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

  • Headings should not be empty (2 elements)

    Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

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

1 checks passed
  • 48 automated accessibility rules passed

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

SEO

1 to fixGoogle 9298
  • 8 links crawlers can't follow

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

  • 48 internal links, 11 external

    The homepage links to 48 pages on averityteam.com and 11 external pages.

8 checks passed
  • Meta description: 141 characters

    Your meta description is 141 characters: “Averity is the top technology recruiting agency based in New York City. We specialize in recruiting for Software, Data,…”.

  • One H1 headline

    Your main headline reads: “Technical Recruiting Agency in New York”.

  • Title: 54 characters

    Your title is a healthy 54 characters: “Averity: Award-Winning NYC Technical Recruiting Agency”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, FAQPage, ImageObject, Organization and Place.

  • 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.averityteam.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: 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,174 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.averityteam.com/llms.txt (2 KiB, 16 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 17 found) and read each the way a search engine does.

1 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

Best practices

3 to fixGoogle 9271
  • 1 broken image

    1 image failed to load on a phone, for example https://www.averityteam.com/.

  • 9 small tap targets

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

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'addEventListener')”.

  • 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

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

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

  • Thin social proof

    Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • 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,665 words of copy

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

6 checks passed
  • 6 calls to action

    The homepage has 6 calls to action, for example “Join our Team”, “Contact Us” and “Learn more about us”.

  • 8 short forms

    8 short forms (5 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

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

  • 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
  • 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). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

  • 5 cookies set on arrival

    5

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

  • 14 other companies contacted

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

Upkeep, stack and company

  • The footer still says © 2023.

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Analytics
Hosting
WP Engine

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 averityteam.com, including 12 speed issues, 1 SEO issue and 3 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