pnc.com website review

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

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

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

About 180 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.

Your mobile performance score is 55 (desktop: 48). Pages that score under 90 lose visitors before the first paint.

8 third-party services load with your homepage (mPulse, Adobe Tag Manager and Facebook and others), adding 790 KiB and 664 ms of main-thread time.

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

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

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

The page has 1,678 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

12 KiB could be saved by minifying CSS.

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

2 images could be 22 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

4 KiB could be saved by minifying JavaScript.

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.

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

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

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

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

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

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

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

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

Your homepage downloads 4.2 MB in 172 requests on a phone: scripts 2.1 MB (55), fonts 1.2 MB (9) and images 440 KiB (41). Under 2 MB keeps phones on slow connections fast.

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

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

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

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

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

Your title is only 20 characters: “PNC Personal Banking”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 2 <h1> headlines (“Open a Checking Account Online” and “Open a Checking Account Online”). One clear main headline is easier for people and search engines.

The homepage links to 109 pages on pnc.com and 33 external pages.

There is no https://www.pnc.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.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.pnc.com/en/personal-banking/investments-and-retirement/pnci-international.html, whose canonical is https://www.pnc.com/en/personal-banking/wealth-management/international-investment-services.html. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=16003228&Ver=2&mid=1a44e9d4-4852-4f9c-b2e5-46f39419b483&bo=1&sid=881621e0c5e111f1a4351da221b1c2df&vid=88165c60c5e111f1a29e03e0e578d11b&vids=1&msclkid=N&page_path=%2Fen.

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

2 errors were logged to the browser console while the page loaded, for example “Framing 'https://awuse4.advanced-web-analytics.com/' violates the following Content Security Policy directive: "child-s…”.

4 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

Chrome logged issues while loading the page (“Content security policy”).

Large scripts ship without source maps.

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.

Social proof on the homepage: 4 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

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

The homepage shows no opening hours. If customers visit or call, show when.

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

The homepage carries about 907 words of visible text.

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

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

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.

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