weyburncu.ca website review

4 images could be 1.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.7 s faster on a phone.

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

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

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

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

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

6 third-party services load with your homepage (Google Tag Manager, YouTube and Google/Doubleclick Ads and others), adding 559 KiB and 389 ms of main-thread time.

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

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

About 22 KiB of CSS is downloaded but never applied on this page.

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

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.

Your largest element takes 13.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Get ready for safer, smarter banking! Learn how to prepare …”.

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

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

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

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

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

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

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

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

17 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-17, real Chrome visitors' tap response (inp) went from 107 ms to 119 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 5.1 MB in 105 requests on a phone: images 4.1 MB (42), scripts 800 KiB (18) and fonts 95 KiB (2). Under 2 MB keeps phones on slow connections fast.

3 images (309 KiB) 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.

3 images further down the page (239 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.45 g of CO₂e: 174.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

[role="img"] and [role="image"] elements must have alternative text: 2 elements on the page fail this check, rated serious by axe-core.

7 images have no alt text, which hurts accessibility and image search.

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

Headings should not be empty: 8 elements on the page fail this check, rated minor by axe-core.

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

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 12 <h1> headlines (“Get Ready for”, “Safer, Smarter” and “Banking!”). One clear main headline is easier for people and search engines.

Your meta description is 382 characters; Google truncates after about 160, so the end of your pitch is cut.

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

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

The homepage links to 84 pages on weyburncu.ca and 16 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

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

https://www.weyburncu.ca/en/solutions/borrowing has no <title>, so Google invents the link text in results.

https://www.weyburncu.ca/en/solutions/investing/boost-your-investing-savvy is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.weyburncu.ca/en/solutions and / all use the title “Weyburn Credit Union - Personal & Business Banking”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.weyburncu.ca/en/meet-with-us, https://www.weyburncu.ca/en/solutions/borrowing, https://www.weyburncu.ca/en/solutions/investing/pacs and https://www.weyburncu.ca/en/solutions/investing/clone-guide-to-saving-for-retirement have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.weyburncu.ca/en/solutions/investing and https://www.weyburncu.ca/en/solutions/investing/clone-investing use the same meta description. A description written for each page earns more clicks.

Your homepage links to 3 pages by a URL that isn't their canonical one, for example /, whose canonical is https://www.weyburncu.ca/en/solutions. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.weyburncu.ca/en/meet-with-us, https://www.weyburncu.ca/en/solutions/borrowing and https://www.weyburncu.ca/en/solutions/investing/boost-your-investing-savvy have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://www.weyburncu.ca/media/1267/main_white-copy.svg.

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

6 errors were logged to the browser console while the page loaded, for example “Loading the script 'https://tag.brandcdn.com/autoscript/weyburncreditunion_vgxsuk1vouvrwgc9/Weyburn_Credit_Union.js' vi…”.

1 image is served at too low a resolution for sharp phone screens.

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

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 406 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

Before a visitor clicks anything, the page loads Google Ads, 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.

Opening the homepage sets 7 cookies, 1 of them by other companies (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 8 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.