Website review, no card needed

penncommunitybank.com logo

penncommunitybank.com website review

Visit site (opens in a new tab)Reviewed 19 November 202644 issues · 90 checks

This review found 44 issues worth fixing on penncommunitybank.com, 18 of them high impact, across 90 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
3.3 s2.6 sMay 30Nov 142.7 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.7 s
Jun 6, 20262.8 s
Jun 13, 20263.0 s
Jun 20, 20263.2 s
Jun 27, 20263.2 s
Jul 4, 20263.2 s
Jul 11, 20263.1 s
Jul 18, 20263.0 s
Jul 25, 20263.0 s
Aug 1, 20262.9 s
Aug 8, 20263.0 s
Aug 15, 20263.0 s
Aug 22, 20262.9 s
Aug 29, 20262.9 s
Sep 5, 20262.9 s
Sep 12, 20263.0 s
Sep 19, 20263.0 s
Sep 26, 20263.0 s
Oct 3, 20262.9 s
Oct 10, 20262.8 s
Oct 17, 20262.7 s
Oct 24, 20262.7 s
Oct 31, 20262.7 s
Nov 7, 20262.8 s
Nov 14, 20262.7 s
Real-visitor tap response (INP)75th percentile, phones
166 ms131 msMay 30Nov 14135 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026158 ms
Jun 6, 2026160 ms
Jun 13, 2026162 ms
Jun 20, 2026161 ms
Jun 27, 2026159 ms
Jul 4, 2026154 ms
Jul 11, 2026145 ms
Jul 18, 2026140 ms
Jul 25, 2026139 ms
Aug 1, 2026138 ms
Aug 8, 2026142 ms
Aug 15, 2026144 ms
Aug 22, 2026145 ms
Aug 29, 2026146 ms
Sep 5, 2026145 ms
Sep 12, 2026145 ms
Sep 19, 2026141 ms
Sep 26, 2026137 ms
Oct 3, 2026138 ms
Oct 10, 2026137 ms
Oct 17, 2026135 ms
Oct 24, 2026140 ms
Oct 31, 2026136 ms
Nov 7, 2026135 ms
Nov 14, 2026135 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 penncommunitybank.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. penncommunitybank.com at 0.6 s0.6 s
  2. penncommunitybank.com at 1.1 s1.1 s
  3. penncommunitybank.com at 1.7 s1.7 s
  4. penncommunitybank.com at 2.3 s2.3 s
  5. penncommunitybank.com at 2.8 s2.8 s
  6. penncommunitybank.com at 3.4 s3.4 s
  7. penncommunitybank.com at 4.0 s4.0 s
  8. penncommunitybank.com at 4.5 s4.5 s

Speed

14 to fix20
  • Reduce unused JavaScript

    3.7 s · 903 KiB

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

  • Render-blocking requests

    1.9 s

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

  • Use efficient cache lifetimes

    1.2 s · 645 KiB

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

  • Mobile performance score: 20

    20/100

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

  • Main-thread work: 5.5 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google CDN, Google Tag Manager and Accessibe Accessibility Overlay and others), adding 1.5 MB and 2.0 s of main-thread time.

  • Reduce unused CSS

    750 ms · 165 KiB

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

  • Google CDN adds 551 ms

    551 ms

    Google CDN costs a phone 551 ms of main-thread work and 742 KiB 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.

  • Improve image delivery

    622 KiB

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

  • Google Tag Manager adds 445 ms

    445 ms

    Google Tag Manager costs a phone 445 ms of main-thread work and 373 KiB 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.

  • Accessibe Accessibility Overlay adds 388 ms

    388 ms

    Accessibe Accessibility Overlay costs a phone 388 ms of main-thread work and 251 KiB 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.

  • FontAwesome CDN adds 351 ms

    351 ms

    FontAwesome CDN costs a phone 351 ms of main-thread work and 89 KiB 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.

  • 20 long tasks on the main thread

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

  • 2,320 HTML elements

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

  • Font display

    50 ms

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

  • Legacy JavaScript

    7 KiB

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

    2 KiB

    2 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 22 ms

    22 ms

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

Core Web Vitals

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

  • Largest Contentful Paint: 14.0 s

    14.0 s

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

  • Time to Interactive: 19.8 s

    19.8 s

    The page becomes fully interactive after 19.8 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.

  • Total Blocking Time: 1.2 s

    1.2 s

    Scripts block taps and scrolling for 1.2 s in total while the page loads. Good is under 200 ms.

  • First Contentful Paint: 4.1 s

    4.1 s

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

  • Cumulative Layout Shift: 0.284

    0.284

    The layout shifts by 0.284 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Real-user CLS: 0.18

    0.18

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

  • 5 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    -1%

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

5 checks passed
  • Real-user LCP: 2.0 s

    2.0 s

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

  • Real-user INP: 128 ms

    128 ms

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

  • Real-user FCP: 1.5 s

    1.5 s

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

  • Real-user TTFB: 523 ms

    523 ms

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

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

    -15%

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

Images and page weight

5 to fix33
  • 1 image over 500 KB

    [email protected] weighs 649 KiB. On a phone connection a single image that size takes seconds.

  • 2 images far larger than shown

    576 KiB

    2 images are downloaded at several times the size a phone draws them, for example [email protected] at 3,202 px wide, shown at 390 px. Resized copies would save about 576 KiB.

  • Page weight: 3.6 MB in 144 requests

    3.6 MB

    Your homepage downloads 3.6 MB in 144 requests on a phone: scripts 1.6 MB (41), images 1.1 MB (23) and other files 471 KiB (39). Under 2 MB keeps phones on slow connections fast.

  • 5 images in older formats

    5 images (1.0 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.

  • 2 images below the first screen load straight away

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

  • About 1.0 g of CO₂ per visit

    1.01 g

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

Accessibility

6 to fixGoogle 8992
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 12 text elements with low contrast

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

  • 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 (2 elements)

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

  • 15 links without text

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

  • 3 form fields without a label

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

  • 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
  • 51 automated accessibility rules passed

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

SEO

4 to fixGoogle 7784
  • Title is long (75 characters)

    Your title is 75 characters, so Google will cut it off around 60: “Personal & Business Banking Solutions In Bucks County | Penn Community Bank”.

  • 2 H1 headlines

    There are 2 <h1> headlines (“Home Equity Loans As low as 6.99% APR* 10 Year Te…” and “Built for Business. Backed by Community.”). One clear main headline is easier for people and search engines.

  • 28 links crawlers can't follow

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

  • 4 links with vague text

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

  • 151 internal links, 9 external

    The homepage links to 151 pages on penncommunitybank.com and 9 external pages.

6 checks passed
  • Meta description: 153 characters

    Your meta description is 153 characters: “Penn Community Bank is the top community bank for personal, small business and commercial business banking in Bucks, Mo…”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, 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://www.penncommunitybank.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: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (656 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.penncommunitybank.com/llms.txt (6 KiB, 48 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90
  • 2 pages without a meta description

    https://www.penncommunitybank.com/resources/financial-calculators/mortgage/calculate-a-mortgage-payment and https://www.penncommunitybank.com/resources/financial-quizzes/budgeting-basics have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages without an H1

    https://www.penncommunitybank.com/resources/financial-calculators/mortgage/calculate-a-mortgage-payment, https://www.penncommunitybank.com/resources/financial-quizzes/budgeting-basics and https://www.penncommunitybank.com/find-a-location have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

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

  • 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

3 to fixGoogle 7376
  • 1 broken image

    1 image failed to load on a phone, for example https://jelly.mdhv.io/v1/star.gif?pid=bL687uv6hBczqzx6Bc1SOm6GwhJ9&src=mh&evt=hi.

  • 2 third-party cookies

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

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.

  • Browser-reported issues

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

2 checks passed
  • Tap targets are thumb-sized

    175 of 183 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix92
  • Thin social proof

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

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

    The homepage carries about 856 words of visible text.

5 checks passed
  • Clear next step on the first screen

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

  • 7 calls to action

    The homepage has 7 calls to action, for example “Contact Us”, “Apply for a Loan” and “Learn More”.

  • 4 short forms

    4 short forms (2 fields at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

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

Privacy and tracking

  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager and The Trade Desk (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.

  • 6 cookies set on arrival

    6

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

  • 23 other companies contacted

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

1 checks passed
  • Consent tool: CookieYes

    A consent management tool (CookieYes) 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 penncommunitybank.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Tag Manager
Hosting
Sucuri

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 44 issues on penncommunitybank.com, including 23 speed issues, 4 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