Website review, no card needed

pgimquantitativesolutions.com logo

pgimquantitativesolutions.com website review

Visit site (opens in a new tab)Reviewed 26 October 202642 issues · 66 checks

This review found 42 issues worth fixing on pgimquantitativesolutions.com, 22 of them high impact, across 66 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
4.5 s2.8 sJun 20Oct 244.3 s
Show as table
DateReal-visitor load time (LCP)
Jun 20, 20263.6 s
Jun 27, 20263.3 s
Jul 11, 20263.2 s
Jul 18, 20263.0 s
Aug 8, 20263.2 s
Aug 15, 20263.2 s
Aug 22, 20263.3 s
Aug 29, 20263.4 s
Sep 5, 20263.5 s
Sep 12, 20263.7 s
Sep 19, 20263.8 s
Sep 26, 20264.1 s
Oct 3, 20264.2 s
Oct 10, 20264.3 s
Oct 17, 20264.3 s
Oct 24, 20264.3 s
Real-visitor tap response (INP)75th percentile, phones
319 ms226 msJun 20Oct 24307 ms
Show as table
DateReal-visitor tap response (INP)
Jun 20, 2026254 ms
Jun 27, 2026258 ms
Jul 11, 2026263 ms
Jul 18, 2026261 ms
Aug 8, 2026237 ms
Aug 15, 2026237 ms
Aug 22, 2026238 ms
Aug 29, 2026237 ms
Sep 5, 2026237 ms
Sep 12, 2026250 ms
Sep 19, 2026271 ms
Sep 26, 2026304 ms
Oct 3, 2026308 ms
Oct 10, 2026308 ms
Oct 17, 2026307 ms
Oct 24, 2026307 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 pgimquantitativesolutions.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. pgimquantitativesolutions.com at 0.5 s0.5 s
  2. pgimquantitativesolutions.com at 1.0 s1.0 s
  3. pgimquantitativesolutions.com at 1.5 s1.5 s
  4. pgimquantitativesolutions.com at 2.0 s2.0 s
  5. pgimquantitativesolutions.com at 2.6 s2.6 s
  6. pgimquantitativesolutions.com at 3.1 s3.1 s
  7. pgimquantitativesolutions.com at 3.6 s3.6 s
  8. pgimquantitativesolutions.com at 4.1 s4.1 s

Speed

6 to fix30
  • Reduce unused JavaScript

    8.8 s · 1.7 MB

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

  • Avoid multiple page redirects

    3.8 s

    The page goes through 3 redirects before it starts loading, costing about 3.8 s. Link and advertise the final URL directly.

  • Mobile performance score: 30

    30/100

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

  • Main-thread work: 6.3 s

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

  • 20 long tasks on the main thread

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

  • Reduce unused CSS

    300 ms · 81 KiB

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

  • 1 third-party service on the page

    1 third-party service load with your homepage (Adobe Tag Manager), adding 127 KiB and 0 ms of main-thread time.

1 checks passed
  • Server response: 52 ms

    52 ms

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

Core Web Vitals

13 to fix33
  • 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.3 s

    4.3 s

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

  • Real-user FCP: 3.9 s

    3.9 s

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

  • Real-user TTFB: 2.6 s

    2.6 s

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

  • First Contentful Paint: 13.1 s

    13.1 s

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

  • Largest Contentful Paint: 26.1 s

    26.1 s

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

  • Time to Interactive: 40.5 s

    40.5 s

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

  • Speed Index: 14.5 s

    14.5 s

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

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

  • Real-user INP: 307 ms

    307 ms

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

  • Tap response (INP) got 20% slower for real visitors

    +20%

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

  • Largest content (LCP) got 24% slower for real visitors

    +24%

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

  • 5 images without width and height

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

2 checks passed
  • Real-user CLS: 0.02

    0.02

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

3 to fix40
  • Page weight: 6.4 MB in 255 requests

    6.4 MB

    Your homepage downloads 6.4 MB in 255 requests on a phone: scripts 4.2 MB (99), images 1.3 MB (63) and fonts 558 KiB (7). Under 2 MB keeps phones on slow connections fast.

  • 2 images far larger than shown

    543 KiB

    2 images are downloaded at several times the size a phone draws them, for example David-Blanchett-Interview-V-01.png at 8,071 px wide, shown at 390 px. Resized copies would save about 543 KiB.

  • 2 images in older formats

    2 images (794 KiB) 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.

  • 6 images below the first screen load straight away

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

  • About 1.8 g of CO₂ per visit

    1.82 g

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

Accessibility

1 to fixGoogle 9697
  • ARIA dialog and alertdialog nodes should have an accessible name (1 element)

    ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

1 checks passed
  • 36 automated accessibility rules passed

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

SEO

11 to fixGoogle 8539
  • Page is set to noindex

    The robots meta tag says “noindex, nofollow”: Google is told not to list this page at all.

  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No H1 headline

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

  • 109 links crawlers can't follow

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

  • Title is short (6 characters)

    Your title is only 6 characters: “Router”. 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.

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

  • Only 0 internal links

    The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • 5 links with vague text

    5 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • No X (Twitter) card tag

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

2 checks passed
  • 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.pgim.com/sitemap-us.xml.

AI search readiness

2 to fix63
  • Most text only appears after JavaScript runs

    0%

    A phone browser shows 1,117 words, but the HTML your server sends has only 0. 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.pgim.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.

Best practices

2 to fixGoogle 7391
  • 7 small tap targets

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

  • 2 third-party cookies

    2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • Browser-reported issues

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

  • Missing source maps

    Large scripts ship without source maps.

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

4 to fix40
  • No calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach 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 1,117 words of copy

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

1 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Contact Us”.

Privacy and tracking

  • 7 trackers load before any consent

    7

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

  • 27 cookies set on arrival

    27

    Opening the homepage sets 27 cookies (measured from a US location before any click).

  • 35 other companies contacted

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

Upkeep, stack and company

Stack

Hosting
Imperva

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 42 issues on pgimquantitativesolutions.com, including 19 speed issues, 11 SEO issues and 4 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