Website review, no card needed
mybank.com website review
Visit site (opens in a new tab)Reviewed 2 November 202641 issues · 88 checks
This review found 41 issues worth fixing on mybank.com, 16 of them high impact, across 88 checks. The most urgent: improve image delivery. 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
72CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 4.6 s |
| May 23, 2026 | 4.6 s |
| May 30, 2026 | 4.7 s |
| Jun 6, 2026 | 4.6 s |
| Jun 13, 2026 | 4.3 s |
| Jun 20, 2026 | 4.2 s |
| Jun 27, 2026 | 4.3 s |
| Jul 4, 2026 | 4.3 s |
| Jul 11, 2026 | 4.4 s |
| Jul 18, 2026 | 4.4 s |
| Jul 25, 2026 | 4.4 s |
| Aug 1, 2026 | 4.5 s |
| Aug 8, 2026 | 4.5 s |
| Aug 15, 2026 | 4.4 s |
| Aug 22, 2026 | 4.6 s |
| Aug 29, 2026 | 4.7 s |
| Sep 5, 2026 | 4.7 s |
| Sep 12, 2026 | 4.8 s |
| Sep 19, 2026 | 4.6 s |
| Sep 26, 2026 | 4.7 s |
| Oct 3, 2026 | 4.9 s |
| Oct 10, 2026 | 4.9 s |
| Oct 17, 2026 | 4.9 s |
| Oct 24, 2026 | 4.9 s |
| Oct 31, 2026 | 5.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 3.0 s |
| May 23, 2026 | 2.8 s |
| May 30, 2026 | 2.3 s |
| Jun 6, 2026 | 1.4 s |
| Jun 13, 2026 | 254 ms |
| Jun 20, 2026 | 169 ms |
| Jun 27, 2026 | 154 ms |
| Jul 4, 2026 | 145 ms |
| Jul 11, 2026 | 144 ms |
| Jul 18, 2026 | 139 ms |
| Jul 25, 2026 | 138 ms |
| Aug 1, 2026 | 138 ms |
| Aug 8, 2026 | 138 ms |
| Aug 15, 2026 | 144 ms |
| Aug 22, 2026 | 144 ms |
| Aug 29, 2026 | 142 ms |
| Sep 5, 2026 | 139 ms |
| Sep 12, 2026 | 138 ms |
| Sep 19, 2026 | 138 ms |
| Sep 26, 2026 | 144 ms |
| Oct 3, 2026 | 153 ms |
| Oct 10, 2026 | 156 ms |
| Oct 17, 2026 | 158 ms |
| Oct 24, 2026 | 156 ms |
| Oct 31, 2026 | 154 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
Speed
Improve image delivery
3.0 s · 789 KiB5 images could be 789 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.0 s faster on a phone.
Render-blocking requests
2.2 s21 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.2 s.
Mobile performance score: 30
30/100Your mobile performance score is 30. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Use efficient cache lifetimes
3.0 MB17 files are served with short cache lifetimes, so returning visitors download them again (3.0 MB).
Reduce unused JavaScript
600 ms · 1.5 MBAbout 1.5 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (GitHub, Google Tag Manager and Clarity and others), adding 3.2 MB and 1.1 s of main-thread time.
GitHub adds 575 ms
575 msGitHub costs a phone 575 ms of main-thread work and 2.9 MB 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
450 ms · 196 KiBAbout 196 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 624 ms. During a long task the page ignores taps.
Main-thread work: 3.2 s
A phone's processor spends 3.2 s on main-thread work while loading, 1.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
1,804 HTML elements
The page has 1,804 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Font display
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
Legacy JavaScript
6 KiBPolyfills for old browsers add 6 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
5 KiB5 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 3 ms
3 msYour server sent the HTML in 3 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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: 5.1 s
5.1 sReal visitors wait 5.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 4.5 s
4.5 sReal visitors see the first content after 4.5 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 3.7 s
3.7 sReal visitors wait 3.7 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 13.0 s
13.0 sYour largest element takes 13.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Impersonation Check Scam Targeting B…”. Most of its time is resource load delay (9.3 s).
Speed Index: 15.9 s
15.9 sVisually, the page fills in at 15.9 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 13.1 s
13.1 sThe page becomes fully interactive after 13.1 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.304
0.304The layout shifts by 0.304 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Total Blocking Time: 718 ms
718 msScripts block taps and scrolling for 718 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 2.3 s
2.3 sThe first text or image appears after 2.3 s on a phone. Good is under 1.8 s.
2 images without width and height
2 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
+8%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 4.6 s to 5.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user INP: 150 ms
150 msReal visitors wait 150 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.02
0.02For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.
Tap response (INP) got 95% faster for real visitors
-95%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 3.0 s to 154 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 6.1 MB in 172 requests
6.1 MBYour homepage downloads 6.1 MB in 172 requests on a phone: scripts 3.4 MB (43), images 1.6 MB (30) and fonts 830 KiB (9). Under 2 MB keeps phones on slow connections fast.
About 1.7 g of CO₂ per visit
1.72 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.72 g of CO₂e: 206.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
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
14 tap targets too small
14 tap targets are too small or too close together to hit reliably with a finger.
8 text elements with low contrast
8 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.
All page content should be contained by landmarks (15 elements)
All page content should be contained by landmarks: 15 elements on the page fail this check, rated moderate by axe-core.
Heading levels should only increase by one (1 element)
Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
4 links without text
4 visible links have no text or label, so screen readers cannot say where they go.
2 checks passed
Every image has alt text
All 24 images in the HTML carry an alt attribute.
39 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 39 passed and 8 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
3 H1 headlines
There are 3 <h1> headlines (“Impersonation Check Scam Targeting Business Custo…”, “Open a YouFirst Account Online Today!” and “Banking for a Better Tomorrow.”). One clear main headline is easier for people and search engines.
12 links with vague text
12 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
137 internal links, 38 external
The homepage links to 137 pages on mybank.com and 38 external pages.
7 checks passed
Meta description: 111 characters
Your meta description is 111 characters: “At First United, we believe our work has a purpose, delivering an uncommon commitment to service and solutions.”.
Title: 32 characters
Your title is a healthy 32 characters: “Home - First United Bank & Trust”.
Canonical URL set
The canonical URL is https://mybank.com/.
Structured data in place
Structured data found: BreadcrumbList, Event, ImageObject, Organization 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://mybank.com/sitemap_index.xml.
AI search readiness
No llms.txt
There is no https://mybank.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.
3 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 (1,069 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages without a meta description
https://mybank.com/personal/student-hub and https://mybank.com/event-directory have no meta description, so Google writes the search snippet from whatever text it finds.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://mybank.com/event-directory, whose canonical is https://mybank.com/events. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
2 pages slow to respond
https://mybank.com/security and https://mybank.com/locations took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 99 found) and read each the way a search engine does.
5 checks passed
Linked pages load
14 pages of 15 loaded without an error (the rest turned automated requests away).
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 14 pages that loaded have a <title>.
Best practices
6 small tap targets
6 of 18 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.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
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.
About 549 words of copy
The homepage carries about 549 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Learn more.”.
5 calls to action
The homepage has 5 calls to action, for example “Contact Us”, “Check Order” and “Learn more.”.
Analytics in place
Analytics detected: Google Tag Manager and LinkedIn Insight.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Tag Manager, Microsoft Clarity 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.
5 cookies set on arrival
5Opening the homepage sets 5 cookies (measured from a US location before any click).
30 other companies contacted
Loading the homepage contacts 30 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 mybank.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 | Microsoft Clarity
- Hosting
- AWS
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 41 issues on mybank.com, including 22 speed issues, 3 SEO issues and 2 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.