Website review, no card needed

47billion.com logo

47billion.com website review

Visit site (opens in a new tab)Reviewed 3 November 202617 issues · 89 checks

This review found 17 issues worth fixing on 47billion.com, 7 of them high impact, across 89 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.9 s2.8 sMay 16Oct 313.5 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20263.7 s
May 23, 20263.8 s
May 30, 20263.8 s
Jun 6, 20263.8 s
Jun 13, 20263.6 s
Jun 20, 20263.3 s
Jun 27, 20263.2 s
Jul 4, 20263.0 s
Jul 11, 20263.0 s
Jul 18, 20263.0 s
Jul 25, 20263.1 s
Aug 1, 20263.2 s
Aug 8, 20263.2 s
Aug 15, 20263.2 s
Aug 22, 20263.1 s
Aug 29, 20263.1 s
Sep 5, 20263.2 s
Sep 12, 20263.3 s
Sep 19, 20263.4 s
Sep 26, 20263.7 s
Oct 3, 20263.7 s
Oct 10, 20263.7 s
Oct 17, 20263.7 s
Oct 24, 20263.6 s
Oct 31, 20263.5 s
Real-visitor tap response (INP)75th percentile, phones
207 ms136 msMay 16Oct 31149 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026184 ms
May 23, 2026186 ms
May 30, 2026189 ms
Jun 6, 2026186 ms
Jun 13, 2026196 ms
Jun 20, 2026186 ms
Jun 27, 2026178 ms
Jul 4, 2026177 ms
Jul 11, 2026177 ms
Jul 18, 2026177 ms
Jul 25, 2026182 ms
Aug 1, 2026172 ms
Aug 8, 2026172 ms
Aug 15, 2026187 ms
Aug 22, 2026182 ms
Aug 29, 2026199 ms
Sep 5, 2026188 ms
Sep 12, 2026148 ms
Sep 19, 2026156 ms
Sep 26, 2026160 ms
Oct 3, 2026158 ms
Oct 10, 2026158 ms
Oct 17, 2026146 ms
Oct 24, 2026144 ms
Oct 31, 2026149 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 47billion.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

47billion.com does not allow embedding, so this is Google's rendering of the page.

Speed

2 to fix90
  • Render-blocking requests

    1.7 s

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

  • Reduce unused CSS

    600 ms · 115 KiB

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

  • 4 third-party services on the page

    4 third-party services load with your homepage (Google Tag Manager, Clarity and piwik.pro and others), adding 213 KiB and 247 ms of main-thread time.

  • Reduce unused JavaScript

    152 KiB

    About 152 KiB of JavaScript is downloaded but never used on this page.

  • 3 long tasks on the main thread

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

  • Use efficient cache lifetimes

    10 KiB

    1 file is served with short cache lifetimes, so returning visitors download them again (10 KiB).

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

3 checks passed
  • Mobile performance score: 90

    90/100

    Your mobile performance score is 90. That is in Google's “good” band (90 and up).

  • Main-thread work: 1.4 s

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

  • Server response: 30 ms

    30 ms

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

Core Web Vitals

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

  • Real-user LCP: 4.0 s

    4.0 s

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

  • Real-user FCP: 3.7 s

    3.7 s

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

  • Real-user TTFB: 2.0 s

    2.0 s

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

  • Time to Interactive: 5.5 s

    5.5 s

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

  • Largest Contentful Paint: 3.1 s

    3.1 s

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

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

  • Largest content (LCP) held steady for real visitors

    -5%

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

6 checks passed
  • Real-user INP: 129 ms

    129 ms

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

  • Real-user CLS: 0.02

    0.02

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

  • Tap response (INP) got 21% faster for real visitors

    -21%

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

  • Speed Index: 3.4 s

    3.4 s

    Visually, the page fills in at 3.4 s (Speed Index), inside the 3.4 s “good” threshold.

  • Total Blocking Time: 132 ms

    132 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

100
  • About 0.5 g of CO₂ per visit

    0.47 g

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

4 checks passed
  • Page weight: 1.7 MB in 54 requests

    1.7 MB

    Your homepage downloads 1.7 MB in 54 requests on a phone: media 836 KiB (1), scripts 478 KiB (22) and stylesheets 156 KiB (4). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • 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

2 to fixGoogle 9596
  • 15 text elements with low contrast

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

  • 2 images without alt text

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

  • Headings skip levels

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

1 checks passed
  • 47 automated accessibility rules passed

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

SEO

2 to fixGoogle 9288
  • Title is long (73 characters)

    Your title is 73 characters, so Google will cut it off around 60: “Enterprise Product Development, AI & Data Engineering Experts | 47Billion”.

  • Meta description is long (167 characters)

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

  • 102 internal links, 9 external

    The homepage links to 102 pages on 47billion.com and 9 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “HUMAN-FIRST”.

  • Canonical URL set

    The canonical URL is https://47billion.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://47billion.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,099 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes /llms.txt (4 KiB, 0 links), a plain-text guide to the site for AI tools.

Other pages

1 to fix95
  • 2 pages without an H1

    /our-work and /careers have no <h1> headline, so visitors and search engines get no clear main topic.

  • 4 pages slow to respond

    /ai-ml, /user-experience-design, /us-staffing and /financial-services took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

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

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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

1 to fixGoogle 9293
  • 2 JavaScript errors while loading

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

  • 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

    6 of 7 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Security and trust

100
  • No security.txt

    There is no /.well-known/security.txt telling researchers how to report a security problem to you.

8 checks passed
  • Served over HTTPS

    The homepage is served over HTTPS (47billion.com).

  • Valid certificate (48 days left)

    The certificate from Sectigo Limited · Sectigo Public Server Authentication CA DV R36 verifies for 47billion.com and is valid for another 48 days.

  • Protected from clickjacking

    X-Frame-Options or a frame-ancestors policy stops other sites framing yours.

  • Content-Security-Policy set

    A Content-Security-Policy is set, the main browser-side defence against injected scripts.

  • HSTS enabled

    Strict-Transport-Security is set, so browsers always use https.

  • http:// redirects to https

    http://47billion.com redirects to the secure version.

  • HTTP/2

    The server speaks HTTP/2, so browsers load many files over one connection.

  • All 46 links work

    All 46 links checked from your homepage (37 internal, 9 external) answered without errors.

Domain and trust

  • No CAA record

    47billion.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

  • DNSSEC is off

    47billion.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

2 checks passed
  • Domain is 12 years old

    12 years

    47billion.com was registered in Jan 2014 through Name.com, Inc.. An established domain carries more trust with email providers and search engines.

  • Registered until Jan 2028

    47billion.com is registered until Jan 2028.

Content and conversion

1 to fix90
  • Thin social proof

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

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

    The homepage carries about 893 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: “Book a Discovery Call”.

  • 5 calls to action

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

  • Analytics in place

    Analytics detected: Google Analytics and Microsoft Clarity.

  • Direct contact links

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

Email authentication

85
  • Email authentication score: 85/100

    Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

3 checks passed
  • DMARC policy: quarantine

    DMARC tells receivers to quarantine mail that fails authentication.

  • SPF in place (~all)

    An SPF record lists your sending servers and marks other mail as suspicious (~all): “v=spf1 include:spf.protection.outlook.com include:amazonses.com include:vtigermails.com ~all”.

  • DKIM signing found

    A DKIM key is published (selector “google”, “selector1” and “k1”), so receivers can verify mail really came from you.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

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

  • 8 cookies set on arrival

    8

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

  • 11 other companies contacted

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

Upkeep, stack and company

No signs of neglect in what was checked: the copyright year, CMS and plugin versions, and jQuery.

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Analytics | Microsoft Clarity
Hosting
AWS

Company

Employees
150
Headquarters
Santa Clara

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 17 issues on 47billion.com, including 9 speed issues, 2 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