Website review, no card needed
paulbunyan.net website review
Visit site (opens in a new tab)Reviewed 23 October 202636 issues · 88 checks
This review found 36 issues worth fixing on paulbunyan.net, 10 of them high impact, across 88 checks. The most urgent: render-blocking requests. 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
82BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 4.6 s |
| May 9, 2026 | 4.3 s |
| May 16, 2026 | 4.1 s |
| May 23, 2026 | 4.2 s |
| May 30, 2026 | 3.9 s |
| Jun 6, 2026 | 3.4 s |
| Jun 13, 2026 | 2.9 s |
| Jun 20, 2026 | 2.1 s |
| Jun 27, 2026 | 2.0 s |
| Jul 4, 2026 | 2.0 s |
| Jul 11, 2026 | 2.0 s |
| Jul 18, 2026 | 1.9 s |
| Jul 25, 2026 | 1.9 s |
| Aug 1, 2026 | 2.0 s |
| Aug 8, 2026 | 2.0 s |
| Aug 15, 2026 | 1.9 s |
| Aug 22, 2026 | 2.0 s |
| Aug 29, 2026 | 1.9 s |
| Sep 5, 2026 | 1.9 s |
| Sep 12, 2026 | 2.0 s |
| Sep 19, 2026 | 2.0 s |
| Sep 26, 2026 | 2.0 s |
| Oct 3, 2026 | 1.9 s |
| Oct 10, 2026 | 1.8 s |
| Oct 17, 2026 | 1.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 106 ms |
| May 9, 2026 | 109 ms |
| May 16, 2026 | 110 ms |
| May 23, 2026 | 111 ms |
| May 30, 2026 | 114 ms |
| Jun 6, 2026 | 115 ms |
| Jun 13, 2026 | 117 ms |
| Jun 20, 2026 | 116 ms |
| Jun 27, 2026 | 112 ms |
| Jul 4, 2026 | 111 ms |
| Jul 11, 2026 | 111 ms |
| Jul 18, 2026 | 106 ms |
| Jul 25, 2026 | 107 ms |
| Aug 1, 2026 | 105 ms |
| Aug 8, 2026 | 105 ms |
| Aug 15, 2026 | 112 ms |
| Aug 22, 2026 | 113 ms |
| Aug 29, 2026 | 115 ms |
| Sep 5, 2026 | 114 ms |
| Sep 12, 2026 | 111 ms |
| Sep 19, 2026 | 112 ms |
| Sep 26, 2026 | 114 ms |
| Oct 3, 2026 | 112 ms |
| Oct 10, 2026 | 112 ms |
| Oct 17, 2026 | 112 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
Render-blocking requests
4.7 s25 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.7 s.
Improve image delivery
1.1 s · 248 KiB8 images could be 248 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.
Mobile performance score: 55
55/100Your mobile performance score is 55 (desktop: 63). Pages that score under 90 lose visitors before the first paint.
Minify JavaScript
750 ms · 191 KiB191 KiB could be saved by minifying JavaScript.
Font display
850 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 850 ms).
Reduce unused CSS
450 ms · 219 KiBAbout 219 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.
Reduce unused JavaScript
300 ms · 326 KiBAbout 326 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.
Google Maps adds 89 ms
89 msGoogle Maps costs a phone 89 ms of main-thread work and 335 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.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Google Maps and Silktide and others), adding 672 KiB and 224 ms of main-thread time.
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 88 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
24 KiB3 files are served with short cache lifetimes, so returning visitors download them again (24 KiB).
Minify CSS
12 KiB12 KiB could be saved by minifying CSS.
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: 1.5 s
A phone's processor spends 1.5 s on main-thread work while loading, 574 ms of it running JavaScript. That is comfortably low.
Server response: 57 ms
57 msYour server sent the HTML in 57 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.
Largest Contentful Paint: 13.1 s
13.1 sYour largest element takes 13.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
First Contentful Paint: 5.3 s
5.3 sThe first text or image appears after 5.3 s on a phone. Good is under 1.8 s.
Time to Interactive: 15.5 s
15.5 sThe page becomes fully interactive after 15.5 s. Good is under 3.8 s.
Speed Index: 9.4 s
9.4 sVisually, the page fills in at 9.4 s (Speed Index). Good is under 3.4 s.
Real-user TTFB: 1.0 s
1.0 sReal visitors wait 1.0 s for your server to start answering (75th percentile). Good is under 800 ms.
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) held steady for real visitors
+4%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 106 ms to 112 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 checks passed
Real-user LCP: 2.3 s
2.3 sReal visitors wait 2.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 128 ms
128 msReal visitors wait 128 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.09
0.09For real visitors the layout shifts by 0.09 (75th percentile). Good is under 0.1.
Real-user FCP: 1.8 s
1.8 sReal visitors see the first content after 1.8 s (75th percentile). Good is under 1.8 s.
Largest content (LCP) got 60% faster for real visitors
-60%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 4.6 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.075
0.075The layout barely moves while loading (CLS 0.075, good is under 0.1).
Total Blocking Time: 76 ms
76 msScripts block the page for only 76 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 2.7 MB in 135 requests
2.7 MBYour homepage downloads 2.7 MB in 135 requests on a phone: scripts 1.1 MB (63), images 1.1 MB (26) and stylesheets 290 KiB (27). Under 2 MB keeps phones on slow connections fast.
About 0.8 g of CO₂ per visit
0.77 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.77 g of CO₂e: 92.6 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
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.
All page content should be contained by landmarks (23 elements)
All page content should be contained by landmarks: 23 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.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
2 links without text
2 visible links have no text or label, so screen readers cannot say where they go.
Alternative text of images should not be repeated as text (8 elements)
Alternative text of images should not be repeated as text: 8 elements on the page fail this check, rated minor by axe-core.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 30 images in the HTML carry an alt attribute.
31 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 40 WCAG 2.2 A/AA and best-practice rules on the phone render: 31 passed and 9 failed. 2 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.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
191 internal links, 25 external
The homepage links to 191 pages on paulbunyan.net and 25 external pages.
7 checks passed
Meta description: 154 characters
Your meta description is 154 characters: “A member-owned broadband cooperative providing fiber optic fast Internet up to 10 Gig, television, voice, IT, and we ar…”.
Title: 39 characters
Your title is a healthy 39 characters: “Paul Bunyan Communications → right here”.
Canonical URL set
The canonical URL is https://paulbunyan.net/.
Structured data in place
Structured data found: Organization.
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://paulbunyan.net/sitemap.xml.
AI search readiness
No llms.txt
There is no https://paulbunyan.net/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 description; sameAs (social profiles) and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (669 words), so crawlers that don't run JavaScript still read it.
Other pages
15 pages share a meta description
https://paulbunyan.net/contact-us, https://paulbunyan.net/support, https://paulbunyan.net/cooperative/newsweather, https://paulbunyan.net/how-to-pay-your-paul-bunyan-communications-bill, https://paulbunyan.net/my-services and https://paulbunyan.net/residential and 9 others use the same meta description. A description written for each page earns more clicks.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://paulbunyan.net/gigazoneblastwi-fi, whose canonical is https://paulbunyan.net/gigazonewifi. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
11 pages without an H1
https://paulbunyan.net/contact-us, https://paulbunyan.net/support, https://paulbunyan.net/cooperative/newsweather, https://paulbunyan.net/how-to-pay-your-paul-bunyan-communications-bill, https://paulbunyan.net/my-services and https://paulbunyan.net/residential and 5 others 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 75 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.
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.
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
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 (Not Found)”.
2 checks passed
Tap targets are thumb-sized
12 of 12 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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.
Only about 205 words
The homepage has only about 205 words of visible text; thin pages give Google and first-time buyers little to go on.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SIGN UP”.
16 calls to action
The homepage has 16 calls to action, for example “Contact & Offices”, “Services & Pricing” and “Call Completion FAQ”.
Analytics in place
Analytics detected: Google Analytics.
Direct contact links
Visitors can reach you directly: 7 phone links and 0 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Ads 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.
1 cookie set on arrival
1Opening the homepage sets 1 cookie (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.
15 other companies contacted
Loading the homepage contacts 15 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 paulbunyan.net, 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
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 36 issues on paulbunyan.net, including 15 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.