Website review, no card needed

epnb.com logo

epnb.com website review

Visit site (opens in a new tab)Reviewed 26 October 202619 issues · 96 checks

This review found 19 issues worth fixing on epnb.com, 4 of them high impact, across 96 checks. The most urgent: no call to action on the first screen. 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
2.0 s1.3 sMay 9Oct 241.6 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.4 s
May 16, 20261.4 s
May 23, 20261.6 s
May 30, 20261.7 s
Jun 6, 20261.7 s
Jun 13, 20261.9 s
Jun 20, 20261.8 s
Jun 27, 20261.9 s
Jul 4, 20261.8 s
Jul 11, 20261.8 s
Jul 18, 20261.8 s
Jul 25, 20261.7 s
Aug 1, 20261.7 s
Aug 8, 20261.7 s
Aug 15, 20261.7 s
Aug 22, 20261.7 s
Aug 29, 20261.6 s
Sep 5, 20261.6 s
Sep 12, 20261.6 s
Sep 19, 20261.6 s
Sep 26, 20261.7 s
Oct 3, 20261.7 s
Oct 10, 20261.6 s
Oct 17, 20261.6 s
Oct 24, 20261.6 s
Real-visitor tap response (INP)75th percentile, phones
184 ms103 msMay 9Oct 24171 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026112 ms
May 16, 2026112 ms
May 23, 2026122 ms
May 30, 2026138 ms
Jun 6, 2026156 ms
Jun 13, 2026171 ms
Jun 20, 2026171 ms
Jun 27, 2026168 ms
Jul 4, 2026167 ms
Jul 11, 2026164 ms
Jul 18, 2026167 ms
Jul 25, 2026168 ms
Aug 1, 2026170 ms
Aug 8, 2026169 ms
Aug 15, 2026170 ms
Aug 22, 2026171 ms
Aug 29, 2026171 ms
Sep 5, 2026173 ms
Sep 12, 2026175 ms
Sep 19, 2026172 ms
Sep 26, 2026170 ms
Oct 3, 2026169 ms
Oct 10, 2026167 ms
Oct 17, 2026170 ms
Oct 24, 2026171 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 epnb.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

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

Speed

3 to fix73
  • Mobile performance score: 73

    73/100

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

  • Render-blocking requests

    450 ms

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

  • 1,524 HTML elements

    The page has 1,524 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).

  • 2 third-party services on the page

    2 third-party services load with your homepage (Bootstrap CDN and Adobe TypeKit), adding 190 KiB and 0 ms of main-thread time.

  • Phones get a much slower page than desktops

    Desktop scores 99 but mobile only 73. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

2 checks passed
  • Main-thread work: 0.6 s

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

  • Server response: 27 ms

    27 ms

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

Core Web Vitals

5 to fix100
  • First Contentful Paint: 3.2 s

    3.2 s

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

  • Cumulative Layout Shift: 0.252

    0.252

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

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

    +52%

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

  • Largest Contentful Paint: 3.3 s

    3.3 s

    Your largest element takes 3.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Better opportunities start with a foundation of financial w…”.

  • 6 images without width and height

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

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

    +17%

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

9 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.0 s

    1.0 s

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

  • Real-user INP: 171 ms

    171 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 0.8 s

    0.8 s

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

  • Real-user TTFB: 426 ms

    426 ms

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

  • Speed Index: 3.2 s

    3.2 s

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

  • Time to Interactive: 3.3 s

    3.3 s

    The page is fully interactive after 3.3 s.

  • Total Blocking Time: 0 ms

    0 ms

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

Images and page weight

100
  • About 0.07 g of CO₂ per visit

    0.07 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.07 g of CO₂e: 8.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: 266 KiB in 27 requests

    266 KiB

    Your homepage downloads 266 KiB in 27 requests on a phone: fonts 179 KiB (5), HTML 39 KiB (1) and images 25 KiB (14). 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

4 to fixGoogle 9595
  • [aria-*] attributes do not have valid values

    [aria-*] attributes do not have valid values (2 elements).

  • All page content should be contained by landmarks (7 elements)

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

  • 4 links without text

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

  • 2 form fields without a label

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

  • Headings skip levels

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (13 elements).

2 checks passed
  • Every image has alt text

    All 55 images in the HTML carry an alt attribute.

  • 44 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 45 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 1 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 9294
  • No canonical URL

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

  • 14 links with vague text

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

  • 129 internal links, 23 external

    The homepage links to 129 pages on epnb.com and 23 external pages.

7 checks passed
  • Meta description: 158 characters

    Your meta description is 158 characters: “Ephrata National Bank offers personal, business, and ag banking solutions, plus online and mobile banking, loans, and m…”.

  • One H1 headline

    Your main headline reads: “Your Community Banking Partner.”.

  • Title: 50 characters

    Your title is a healthy 50 characters: “Home | Ephrata National Bank - ENB Financial Corp.”.

  • Structured data in place

    Structured data found: Corporation, Person, WPFooter, WPHeader 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.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.epnb.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: 4 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

100
  • 15 internal pages checked

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

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

  • Every page has an H1

    Each page we checked has a main headline.

  • 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

Google 100100
3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

    50 of 51 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Security and trust

1 to fix94
  • No Content-Security-Policy

    No Content-Security-Policy header, the main browser-side defence against injected scripts.

  • No Permissions-Policy

    No Permissions-Policy header to switch off camera, microphone and location for embedded content.

  • No security.txt

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

7 checks passed
  • Served over HTTPS

    The homepage is served over HTTPS (epnb.com).

  • Valid certificate (59 days left)

    The certificate from Sectigo Limited · Sectigo Public Server Authentication CA OV R36 verifies for epnb.com and is valid for another 59 days.

  • Protected from clickjacking

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

  • HSTS enabled

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

  • http:// redirects to https

    http://epnb.com redirects to the secure version.

  • HTTP/2 and HTTP/3

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

  • All 55 links work

    All 55 links checked from your homepage (40 internal, 15 external) answered without errors.

Domain and trust

  • No CAA record

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

    epnb.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 22 years old

    22 years

    epnb.com was registered in Jan 2004 through Network Solutions, LLC. An established domain carries more trust with email providers and search engines.

  • Registered until Jan 2027

    epnb.com is registered until Jan 2027.

Content and conversion

3 to fix75
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • Local business without LocalBusiness data

    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.

  • A 10-field form

    Your longest form asks for 10 fields (0 required). Every extra field lowers completion.

  • No opening hours

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

  • No map or directions link

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

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

    The homepage carries about 661 words of visible text.

5 checks passed
  • 14 calls to action

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

  • Social proof on the page

    Social proof on the homepage: 2 customer or partner logos and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Tag Manager and Matomo.

  • Direct contact links

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

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Email authentication

1 to fix70
  • DMARC is monitor-only (p=none)

    DMARC is set to p=none, so mail pretending to be epnb.com is still delivered. Add a report address, check the reports, then move to quarantine.

  • Email authentication score: 70/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.

2 checks passed
  • SPF in place (~all)

    An SPF record lists your sending servers and marks other mail as suspicious (~all): “v=spf1 mx ip4:68.178.203.134 ip4:206.71.80.64 a:documatix.com include:secureserver.net include:%{i}.spf.hc5220-75.iphmx…”.

  • DKIM signing found

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

Privacy and tracking

  • 5 trackers load before any consent

    5

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

  • 4 cookies set on arrival

    4

    Opening the homepage sets 4 cookies, 2 of them by other companies (measured from a US location before any click).

  • 19 other companies contacted

    Loading the homepage contacts 19 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.

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 Tag Manager | Matomo

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 19 issues on epnb.com, including 8 speed issues, 2 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