Website review, no card needed

pinpointfund.com logo

pinpointfund.com website review

Visit site (opens in a new tab)Reviewed 25 October 202627 issues · 65 checks

This review found 27 issues worth fixing on pinpointfund.com, 5 of them high impact, across 65 checks. The most urgent: page weight: 17.3 MB in 27 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

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

How it loaded on a phone

  1. pinpointfund.com at 0.5 s0.5 s
  2. pinpointfund.com at 1.0 s1.0 s
  3. pinpointfund.com at 1.5 s1.5 s
  4. pinpointfund.com at 2.0 s2.0 s
  5. pinpointfund.com at 2.5 s2.5 s
  6. pinpointfund.com at 3.0 s3.0 s
  7. pinpointfund.com at 3.5 s3.5 s
  8. pinpointfund.com at 3.9 s3.9 s

Speed

3 to fix94
  • Use efficient cache lifetimes

    950 ms · 17.3 MB

    23 files are served with short cache lifetimes, so returning visitors download them again (17.3 MB).

  • Improve image delivery

    14.3 MB

    6 images could be 14.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Render-blocking requests

    650 ms

    2 files block the first paint until they finish downloading. Deferring or inlining them could save about 650 ms.

  • Reduce unused JavaScript

    150 ms · 161 KiB

    About 161 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • 2 long tasks on the main thread

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

  • Legacy JavaScript

    43 KiB

    Polyfills for old browsers add 43 KiB JavaScript that modern phones do not need.

  • Document request latency

    11 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

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

3 checks passed
  • Mobile performance score: 94

    94/100

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

  • Main-thread work: 0.4 s

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

  • Server response: 221 ms

    221 ms

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

Core Web Vitals

3 to fix99
  • Time to Interactive: 50.4 s

    50.4 s

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

  • Speed Index: 5.7 s

    5.7 s

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

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

4 checks passed
  • Largest Contentful Paint: 2.1 s

    2.1 s

    Your largest element renders in 2.1 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Investing in Asian markets since 1999. Empowering talent an…”.

  • First Contentful Paint: 1.1 s

    1.1 s

    The first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 34 ms

    34 ms

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

Images and page weight

4 to fix25
  • Page weight: 17.3 MB in 27 requests

    17.3 MB

    Your homepage downloads 17.3 MB in 27 requests on a phone: images 16.7 MB (6), scripts 467 KiB (9) and other files 45 KiB (3). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    home1.jpg weighs 5.5 MB. On a phone connection a single image that size takes seconds.

  • 1 image far larger than shown

    5.3 MB

    1 image is downloaded at several times the size a phone draws it, for example home1.jpg at 6,240 px wide, shown at 390 px. Resized copies would save about 5.3 MB.

  • 2 images in older formats

    2 images (5.6 MB) 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 4.9 g of CO₂ per visit

    4.91 g

    By the Sustainable Web Design model, a visit to your homepage emits about 4.91 g of CO₂e: 588.8 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

1 to fixGoogle 9698
  • 2 links without text

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

2 checks passed
  • Every image has alt text

    All 6 images in the HTML carry an alt attribute.

  • 27 automated accessibility rules passed

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

SEO

8 to fixGoogle 8368
  • Title is short (25 characters)

    Your title is only 25 characters: “Pinpoint Asset Management”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • Meta description is short (25 characters)

    Your meta description is only 25 characters: “Pinpoint Asset Management”. 70 to 160 characters is enough to sell the click.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No XML sitemap

    No XML sitemap at https://www.pinpointfund.com/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

    There is no robots.txt at pinpointfund.com/robots.txt, the first file search crawlers ask for.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 11 internal links, 1 external

    The homepage links to 11 pages on pinpointfund.com and 1 external page.

1 checks passed
  • One H1 headline

    Your main headline reads: “Multi-Strategy Platform”.

AI search readiness

1 to fix69
  • 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.pinpointfund.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.

Other pages

3 to fix86
  • 8 pages share a title

    /, https://www.pinpointfund.com/about, https://www.pinpointfund.com/milestones, https://www.pinpointfund.com/news, https://www.pinpointfund.com/leadership and https://www.pinpointfund.com/career and 2 others all use the title “Pinpoint Asset Management”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 7 pages share a meta description

    https://www.pinpointfund.com/about, https://www.pinpointfund.com/milestones, https://www.pinpointfund.com/news, https://www.pinpointfund.com/leadership, https://www.pinpointfund.com/career and https://www.pinpointfund.com/privacy and 1 other use the same meta description. A description written for each page earns more clicks.

  • 7 pages without an H1

    https://www.pinpointfund.com/about, https://www.pinpointfund.com/milestones, https://www.pinpointfund.com/news, https://www.pinpointfund.com/leadership, https://www.pinpointfund.com/contactus and https://www.pinpointfund.com/privacy and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

  • 6 pages with very little text

    https://www.pinpointfund.com/about, https://www.pinpointfund.com/milestones, https://www.pinpointfund.com/news, https://www.pinpointfund.com/leadership, https://www.pinpointfund.com/career and https://www.pinpointfund.com/contactus have 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.

  • 3 pages slow to respond

    https://www.pinpointfund.com/career, https://www.pinpointfund.com/contactus and https://www.pinpointfund.com/privacy took over 3 s to send their HTML from our server.

  • 8 internal pages checked

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

5 checks passed
  • Linked pages load

    All 8 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 8 pages that loaded have a meta description.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 8 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10093
  • 6 small tap targets

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

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix67
  • 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 analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • Only about 29 words

    The homepage has only about 29 words of visible text; thin pages give Google and first-time buyers little to go on.

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

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Learn More”.

  • 3 calls to action

    The homepage has 3 calls to action, for example “Contact Us” and “Learn More”.

  • Direct contact links

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

Privacy and tracking

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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

Upkeep, stack and company

Stack

Framework
Next.js

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 27 issues on pinpointfund.com, including 6 speed issues, 8 SEO issues 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