Website review, no card needed
bismanonline.com website review
Visit site (opens in a new tab)Reviewed 12 October 202653 issues · 97 checks
This review found 53 issues worth fixing on bismanonline.com, 18 of them high impact, across 97 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
59FClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 18, 2026 | 2.2 s |
| Apr 25, 2026 | 2.1 s |
| May 2, 2026 | 2.2 s |
| May 9, 2026 | 2.2 s |
| May 16, 2026 | 2.3 s |
| May 23, 2026 | 2.3 s |
| May 30, 2026 | 2.2 s |
| Jun 6, 2026 | 2.2 s |
| Jun 13, 2026 | 2.3 s |
| Jun 20, 2026 | 2.3 s |
| Jun 27, 2026 | 2.3 s |
| Jul 4, 2026 | 2.3 s |
| Jul 11, 2026 | 2.3 s |
| Jul 18, 2026 | 2.3 s |
| Jul 25, 2026 | 2.3 s |
| Aug 1, 2026 | 2.3 s |
| Aug 8, 2026 | 2.3 s |
| Aug 15, 2026 | 2.3 s |
| Aug 22, 2026 | 2.3 s |
| Aug 29, 2026 | 2.2 s |
| Sep 5, 2026 | 2.2 s |
| Sep 12, 2026 | 2.2 s |
| Sep 19, 2026 | 2.3 s |
| Sep 26, 2026 | 2.3 s |
| Oct 3, 2026 | 2.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 18, 2026 | 154 ms |
| Apr 25, 2026 | 157 ms |
| May 2, 2026 | 162 ms |
| May 9, 2026 | 162 ms |
| May 16, 2026 | 162 ms |
| May 23, 2026 | 161 ms |
| May 30, 2026 | 157 ms |
| Jun 6, 2026 | 156 ms |
| Jun 13, 2026 | 155 ms |
| Jun 20, 2026 | 157 ms |
| Jun 27, 2026 | 159 ms |
| Jul 4, 2026 | 161 ms |
| Jul 11, 2026 | 162 ms |
| Jul 18, 2026 | 163 ms |
| Jul 25, 2026 | 167 ms |
| Aug 1, 2026 | 169 ms |
| Aug 8, 2026 | 171 ms |
| Aug 15, 2026 | 173 ms |
| Aug 22, 2026 | 178 ms |
| Aug 29, 2026 | 180 ms |
| Sep 5, 2026 | 180 ms |
| Sep 12, 2026 | 181 ms |
| Sep 19, 2026 | 181 ms |
| Sep 26, 2026 | 180 ms |
| Oct 3, 2026 | 181 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
1.6 s
3.3 s
4.9 s
6.6 s
8.2 s
9.8 s
11.5 s
13.1 s
Speed
Reduce unused JavaScript
5.9 s · 1.3 MBAbout 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.9 s faster on a phone.
Use efficient cache lifetimes
4.6 s · 1.7 MB101 files are served with short cache lifetimes, so returning visitors download them again (1.7 MB).
Render-blocking requests
5.2 s38 files block the first paint until they finish downloading. Deferring or inlining them could save about 5.2 s.
Minify JavaScript
1.1 s · 68 KiB68 KiB could be saved by minifying JavaScript.
Mobile performance score: 22
22/100Your mobile performance score is 22 (desktop: 56). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 5.0 s
A phone's processor spends 5.0 s on main-thread work while loading, 2.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, intergient.com and confiant-integrations.net and others), adding 3.3 MB and 2.6 s of main-thread time.
Improve image delivery
750 ms · 351 KiB14 images could be 351 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 750 ms faster on a phone.
Reduce unused CSS
600 ms · 117 KiBAbout 117 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.
Google Tag Manager adds 626 ms
626 msGoogle Tag Manager costs a phone 626 ms of main-thread work and 491 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.
intergient.com adds 391 ms
391 msintergient.com costs a phone 391 ms of main-thread work and 471 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.
cloudfront.net adds 314 ms
314 mscloudfront.net costs a phone 314 ms of main-thread work and 1.2 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 423 ms. During a long task the page ignores taps.
confiant-integrations.net adds 380 ms
380 msconfiant-integrations.net costs a phone 380 ms of main-thread work and 175 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.
Facebook adds 371 ms
371 msFacebook costs a phone 371 ms of main-thread work and 252 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.
Legacy JavaScript
300 ms · 71 KiBPolyfills for old browsers add 71 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.
Minify CSS
150 ms · 22 KiB22 KiB could be saved by minifying CSS.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Phones get a much slower page than desktops
Desktop scores 56 but mobile only 22. 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.
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: 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.
Largest Contentful Paint: 19.3 s
19.3 sYour largest element takes 19.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 15.7 s
15.7 sVisually, the page fills in at 15.7 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 24.8 s
24.8 sThe page becomes fully interactive after 24.8 s. Good is under 3.8 s.
First Contentful Paint: 5.8 s
5.8 sThe first text or image appears after 5.8 s on a phone. Good is under 1.8 s.
Total Blocking Time: 1.8 s
1.8 sScripts block taps and scrolling for 1.8 s in total while the page loads. Good is under 200 ms.
Real-user INP: 221 ms
221 msReal visitors wait 221 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.18
0.18For real visitors the layout shifts by 0.18 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.145
0.145The layout shifts by 0.145 while loading, so content jumps under the reader's thumb. Good is under 0.1.
2 images without width and height
2 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 16% slower for real visitors
+16%Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' tap response (inp) went from 154 ms to 181 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+6%Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' largest content (lcp) went from 2.2 s to 2.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user LCP: 2.4 s
2.4 sReal visitors wait 2.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 1.6 s
1.6 sReal visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 698 ms
698 msReal visitors wait 698 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
Page weight: 3.8 MB in 210 requests
3.8 MBYour homepage downloads 3.8 MB in 210 requests on a phone: scripts 2.7 MB (75), images 708 KiB (49) and stylesheets 162 KiB (18). Under 2 MB keeps phones on slow connections fast.
1 image in older formats
1 image (181 KiB) is 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.
About 1.1 g of CO₂ per visit
1.08 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.08 g of CO₂e: 129.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
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
26 text elements with low contrast
26 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
ARIA commands must have an accessible name (1 element)
ARIA commands must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
7 images without alt text
7 images have no alt text, which hurts accessibility and image search.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
6 links without text
6 visible links have no text or label, so screen readers cannot say where they go.
3 form fields without a label
3 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h3 → h5), which makes the page harder to scan with a screen reader.
1 checks passed
41 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: 41 passed and 6 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.
Title is short (29 characters)
Your title is only 29 characters: “BisManOnline Free Classifieds”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
91 internal links, 5 external
The homepage links to 91 pages on bismanonline.com and 5 external pages.
3 checks passed
Meta description: 133 characters
Your meta description is 133 characters: “Free classifieds for North Dakota, South Dakota, Montana and Minnesota. Plus - The largest classifieds in the Bakken Wi…”.
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.bismanonline.com/sitemap-sd-index.xml.
AI search readiness
No Organization structured data
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.
No llms.txt
There is no https://www.bismanonline.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.
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 (554 words), so crawlers that don't run JavaScript still read it.
Other pages
3 pages without a meta description
https://www.bismanonline.com/p/advertise, https://www.bismanonline.com/p/help and https://www.bismanonline.com/p/about have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://www.bismanonline.com/users and https://www.bismanonline.com/bmodefault/action/Contact use the same meta description. A description written for each page earns more clicks.
5 pages without an H1
https://www.bismanonline.com/users, https://www.bismanonline.com/p/advertise, https://www.bismanonline.com/p/help, https://www.bismanonline.com/bmodefault/action/Contact and https://www.bismanonline.com/p/about have no <h1> headline, so visitors and search engines get no clear main topic.
2 pages with very little text
https://www.bismanonline.com/users and https://www.bismanonline.com/stores have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
2 pages slow to respond
https://www.bismanonline.com/p/help and https://www.bismanonline.com/p/about took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 56 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.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
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 13 pages that loaded have a <title>.
Best practices
No mobile viewport
No viewport meta tag, so phones render the desktop layout zoomed out.
26 small tap targets
26 of 45 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_CONNECTION_RESET”.
3 distorted images
3 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
Content and conversion
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.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
Thin social proof
Social proof on the homepage: 4 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 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 269 words of copy
The homepage carries about 269 words of visible text.
3 checks passed
2 calls to action
The homepage has 2 calls to action, for example “Contact Us”.
2 short forms
2 short forms (3 fields at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Meta Pixel.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Amazon Ads, Criteo, Google Ads, Google Analytics and Google Tag Manager and 2 mores (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.
39 cookies set on arrival
39Opening the homepage sets 39 cookies, 1 of them by other companies (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.
53 other companies contacted
Loading the homepage contacts 53 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 bismanonline.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- Analytics
- Google Analytics | Google Tag Manager
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 53 issues on bismanonline.com, including 26 speed issues, 5 SEO issues and 5 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.