Website review, no card needed
qnbbank.com website review
Visit site (opens in a new tab)Reviewed 19 November 202628 issues · 78 checks
This review found 28 issues worth fixing on qnbbank.com, 12 of them high impact, across 78 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
88BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 2.5 s |
| Jun 6, 2026 | 2.6 s |
| Jun 13, 2026 | 2.6 s |
| Jun 20, 2026 | 2.6 s |
| Jun 27, 2026 | 2.6 s |
| Jul 4, 2026 | 2.6 s |
| Jul 11, 2026 | 2.6 s |
| Jul 18, 2026 | 2.6 s |
| Jul 25, 2026 | 2.6 s |
| Aug 1, 2026 | 2.6 s |
| Aug 8, 2026 | 2.5 s |
| Aug 15, 2026 | 2.6 s |
| Aug 22, 2026 | 2.5 s |
| Aug 29, 2026 | 2.5 s |
| Sep 5, 2026 | 2.4 s |
| Sep 12, 2026 | 2.4 s |
| Sep 19, 2026 | 2.4 s |
| Sep 26, 2026 | 2.4 s |
| Oct 3, 2026 | 2.4 s |
| Oct 10, 2026 | 2.3 s |
| Oct 17, 2026 | 2.3 s |
| Oct 24, 2026 | 2.4 s |
| Oct 31, 2026 | 2.4 s |
| Nov 7, 2026 | 2.3 s |
| Nov 14, 2026 | 2.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 142 ms |
| Jun 6, 2026 | 145 ms |
| Jun 13, 2026 | 146 ms |
| Jun 20, 2026 | 146 ms |
| Jun 27, 2026 | 146 ms |
| Jul 4, 2026 | 150 ms |
| Jul 11, 2026 | 151 ms |
| Jul 18, 2026 | 154 ms |
| Jul 25, 2026 | 156 ms |
| Aug 1, 2026 | 157 ms |
| Aug 8, 2026 | 162 ms |
| Aug 15, 2026 | 166 ms |
| Aug 22, 2026 | 167 ms |
| Aug 29, 2026 | 166 ms |
| Sep 5, 2026 | 167 ms |
| Sep 12, 2026 | 163 ms |
| Sep 19, 2026 | 163 ms |
| Sep 26, 2026 | 166 ms |
| Oct 3, 2026 | 162 ms |
| Oct 10, 2026 | 163 ms |
| Oct 17, 2026 | 164 ms |
| Oct 24, 2026 | 164 ms |
| Oct 31, 2026 | 167 ms |
| Nov 7, 2026 | 165 ms |
| Nov 14, 2026 | 163 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
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Reduce unused JavaScript
1.1 s · 873 KiBAbout 873 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.1 s faster on a phone.
Render-blocking requests
1.5 s3 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.5 s.
3,436 HTML elements
The page has 3,436 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (onlineaccess1.com, Google Tag Manager and Google Maps and others), adding 986 KiB and 969 ms of main-thread time.
Mobile performance score: 67
67/100Your mobile performance score is 67. Pages that score under 90 lose visitors before the first paint.
onlineaccess1.com adds 613 ms
613 msonlineaccess1.com costs a phone 613 ms of main-thread work and 188 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.
Main-thread work: 3.1 s
A phone's processor spends 3.1 s on main-thread work while loading, 1.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Google Maps adds 148 ms
148 msGoogle Maps costs a phone 148 ms of main-thread work and 391 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.
Reduce unused CSS
180 KiBAbout 180 KiB of CSS is downloaded but never applied on this page.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 81 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
80 KiB11 files are served with short cache lifetimes, so returning visitors download them again (80 KiB).
Legacy JavaScript
20 KiBPolyfills for old browsers add 20 KiB JavaScript that modern phones do not need.
Minify JavaScript
12 KiB12 KiB could be saved by minifying JavaScript.
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.
1 checks passed
Server response: 14 ms
14 msYour server sent the HTML in 14 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 20.1 s
20.1 sThe page becomes fully interactive after 20.1 s. Good is under 3.8 s.
Speed Index: 10.3 s
10.3 sVisually, the page fills in at 10.3 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 4.4 s
4.4 sThe first text or image appears after 4.4 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 4.4 s
4.4 sYour largest element takes 4.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use cookies for a variety of purposes, including enhanci…”. Most of its time is element render delay (2.3 s).
10 images without width and height
10 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 14% slower for real visitors
+14%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 142 ms to 163 ms 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: 2.5 s
2.5 sReal visitors wait 2.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 179 ms
179 msReal visitors wait 179 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.04
0.04For real visitors the layout shifts by 0.04 (75th percentile). Good is under 0.1.
Real-user FCP: 1.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 383 ms
383 msReal visitors wait 383 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 10% faster for real visitors
-10%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 2.5 s to 2.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 78 ms
78 msScripts block the page for only 78 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.034
0.034The layout barely moves while loading (CLS 0.034, good is under 0.1).
Images and page weight
Page weight: 4.2 MB in 150 requests
4.2 MBYour homepage downloads 4.2 MB in 150 requests on a phone: fonts 1.9 MB (20), scripts 1.4 MB (51) and images 497 KiB (12). Under 2 MB keeps phones on slow connections fast.
About 1.2 g of CO₂ per visit
1.19 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.19 g of CO₂e: 142.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Links look like plain text
1 link inside paragraphs relies on colour alone to stand out.
11 images without alt text
11 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (16 elements)
All page content should be contained by landmarks: 16 elements on the page fail this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.
Main landmark should not be contained in another landmark (1 element)
Main landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one contentinfo landmark (1 element)
Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one main landmark (1 element)
Document should not have more than one main landmark: 1 element on the page fails this check, rated moderate by axe-core.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Headings skip levels
Headings skip levels (h2 → h6), which makes the page harder to scan with a screen reader.
1 checks passed
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 9 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
8 links with vague text
8 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
286 internal links, 17 external
The homepage links to 286 pages on qnbbank.com and 17 external pages.
7 checks passed
Meta description: 145 characters
Your meta description is 145 characters: “Discover QNB Bank's comprehensive range of financial services, including personal and business banking, loans, savings,…”.
Title: 51 characters
Your title is a healthy 51 characters: “QNB Bank | Community Banking at its best since 1877”.
Canonical URL set
The canonical URL is https://www.qnbbank.com/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, Organization, Place and WebPage.
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.qnbbank.com/sitemap_index.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
No llms.txt
There is no https://www.qnbbank.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.
Opted out of AI training for 5 crawlers
robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.
2 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.
Text is in the HTML
Your server sends the page's text in the HTML (1,469 words), so crawlers that don't run JavaScript still read it.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 93 found) and read each the way a search engine does.
1 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Best practices
Missing source maps
Large scripts ship without source maps.
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
34 of 38 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 1 trust badge. 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 410 words of copy
The homepage carries about 410 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “LEARN MORE”.
28 calls to action
The homepage has 28 calls to action, for example “Personal Fee Schedule”, “Business Fee Schedule” and “ACH Deadlines & Fee Schedule”.
11 short forms
11 short forms (7 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Cloudflare Web Analytics.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (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.
3 cookies set on arrival
3Opening the homepage sets 3 cookies (measured from a US location before any click).
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.
9 other companies contacted
Loading the homepage contacts 9 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
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 qnbbank.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 Analytics | Google Tag Manager
- Hosting
- Cloudflare
Hiring
- Hiring
- 20 open roles
- Teams
- Other (3), Operations (2), Customer Service (1)
- Job board
- applicantpro
Company
- Employees
- 184
- Founded
- 1877
- Headquarters
- Quakertown
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 28 issues on qnbbank.com, including 13 speed issues, 2 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.