Website review, no card needed
bnsflogistics.com website review
Visit site (opens in a new tab)Reviewed 26 October 202632 issues · 81 checks
This review found 32 issues worth fixing on bnsflogistics.com, 13 of them high impact, across 81 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
74CClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
0.5 s
0.9 s
1.4 s
1.8 s
2.3 s
2.7 s
3.2 s
3.6 s
Speed
Improve image delivery
4.0 s · 1.7 MB17 images could be 1.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 4.0 s faster on a phone.
Render-blocking requests
3.3 s39 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.3 s.
Reduce unused JavaScript
1.1 s · 295 KiBAbout 295 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.
Mobile performance score: 55
55/100Your mobile performance score is 55 (desktop: 67). Pages that score under 90 lose visitors before the first paint.
Google Tag Manager adds 312 ms
312 msGoogle Tag Manager costs a phone 312 ms of main-thread work and 509 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.
1,820 HTML elements
The page has 1,820 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 (Google Tag Manager, jQuery CDN and Google/Doubleclick Ads and others), adding 618 KiB and 375 ms of main-thread time.
Reduce unused CSS
150 ms · 59 KiBAbout 59 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 158 ms. During a long task the page ignores taps.
Legacy JavaScript
100 ms · 10 KiBPolyfills for old browsers add 10 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 100 ms faster on a phone.
Font display
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
Minify JavaScript
8 KiB8 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.
Use efficient cache lifetimes
2 KiB1 file is served with short cache lifetimes, so returning visitors download them again (2 KiB).
2 checks passed
Main-thread work: 1.6 s
A phone's processor spends 1.6 s on main-thread work while loading, 770 ms of it running JavaScript. That is comfortably low.
Server response: 6 ms
6 msYour server sent the HTML in 6 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 33.4 s
33.4 sYour largest element takes 33.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 33.9 s
33.9 sThe page becomes fully interactive after 33.9 s. Good is under 3.8 s.
Speed Index: 9.6 s
9.6 sVisually, the page fills in at 9.6 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 4.1 s
4.1 sThe first text or image appears after 4.1 s on a phone. Good is under 1.8 s.
Total Blocking Time: 201 ms
201 msScripts block taps and scrolling for 201 ms in total while the page loads. Good is under 200 ms.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
1 checks passed
Cumulative Layout Shift: 0.008
0.008The layout barely moves while loading (CLS 0.008, good is under 0.1).
Images and page weight
Page weight: 7.0 MB in 140 requests
7.0 MBYour homepage downloads 7.0 MB in 140 requests on a phone: images 5.8 MB (40), scripts 838 KiB (48) and stylesheets 163 KiB (37). Under 2 MB keeps phones on slow connections fast.
14 images in older formats
14 images (972 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.
14 images below the first screen load straight away
14 images further down the page (972 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 2.0 g of CO₂ per visit
1.98 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.98 g of CO₂e: 237.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Elements must only use permitted ARIA attributes (1 element)
Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
Positive tabindex
1 element has a tabindex above 0, which scrambles the keyboard order.
All page content should be contained by landmarks (43 elements)
All page content should be contained by landmarks: 43 elements on the page fail 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.
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.
The skip-link target should exist and be focusable (1 element)
The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.
30 links without text
30 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h2 → h4, h3 → h5 and h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 32 images in the HTML carry an alt attribute.
37 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 37 passed and 9 failed. 1 more 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.
29 links with vague text
29 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
121 internal links, 5 external
The homepage links to 121 pages on bnsflogistics.com and 5 external pages.
7 checks passed
Meta description: 152 characters
Your meta description is 152 characters: “BNSF Logistics is a technology and people driven third party logistics company providing smart, creative supply chain s…”.
Title: 40 characters
Your title is a healthy 40 characters: “We Deliver What Matters - BNSF Logistics”.
Canonical URL set
The canonical URL is https://www.bnsflogistics.com/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, Organization, WebPage and WebSite.
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.bnsflogistics.com/sitemap_index.xml.
AI search readiness
No llms.txt
There is no https://www.bnsflogistics.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 (856 words), so crawlers that don't run JavaScript still read it.
Other pages
15 pages without an H1
https://www.bnsflogistics.com/resource-center, https://www.bnsflogistics.com/contact-us, https://www.bnsflogistics.com/projects, https://www.bnsflogistics.com/services/rail, https://www.bnsflogistics.com/services/heavy-haul and https://www.bnsflogistics.com/services/flatbed and 9 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 31 found) and read each the way a search engine does.
6 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.
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
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'addEventListener')”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
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.
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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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 832 words of copy
The homepage carries about 832 words of visible text.
5 checks passed
27 calls to action
The homepage has 27 calls to action, for example “Contact & Support”, “Request a Quote” and “Contact Us”.
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Google Analytics and HubSpot.
Direct contact links
Visitors can reach you directly: 1 phone link 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
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and HubSpot (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.
5 cookies set on arrival
5Opening the homepage sets 5 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.
11 other companies contacted
Loading the homepage contacts 11 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 bnsflogistics.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
- The footer still says © 2013.
Stack
- CMS
- WordPress
- Framework
- Vue.js
- Analytics
- Google Analytics
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 32 issues on bnsflogistics.com, including 11 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.