Website review, no card needed
e-railspot.com website review
Visit site (opens in a new tab)Reviewed 9 November 202634 issues · 81 checks
This review found 34 issues worth fixing on e-railspot.com, 14 of them high impact, across 81 checks. The most urgent: use efficient cache lifetimes. 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
80BClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
1.3 s
2.6 s
3.8 s
5.1 s
6.4 s
7.7 s
9.0 s
10.2 s
Speed
Use efficient cache lifetimes
11.6 s · 41.1 MB105 files are served with short cache lifetimes, so returning visitors download them again (41.1 MB).
Improve image delivery
4.3 s · 34.7 MB41 images could be 34.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.3 s faster on a phone.
Render-blocking requests
8.0 s27 files block the first paint until they finish downloading. Deferring or inlining them could save about 8.0 s.
Reduce unused CSS
3.9 s · 776 KiBAbout 776 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 3.9 s faster on a phone.
Reduce unused JavaScript
2.0 s · 411 KiBAbout 411 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.0 s faster on a phone.
Font display
2.3 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 2.3 s).
Mobile performance score: 54
54/100Your mobile performance score is 54. Pages that score under 90 lose visitors before the first paint.
Minify CSS
550 ms · 103 KiB103 KiB could be saved by minifying CSS.
Main-thread work: 2.8 s
A phone's processor spends 2.8 s on main-thread work while loading, 615 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
1,685 HTML elements
The page has 1,685 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 (Other Google APIs/SDKs, ShareThis and Google Tag Manager and others), adding 626 KiB and 294 ms of main-thread time.
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 118 ms. During a long task the page ignores taps.
Legacy JavaScript
32 KiBPolyfills for old browsers add 32 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: 248 ms
248 msYour server sent the HTML in 248 ms, well inside Google's 600 ms guideline.
Core Web Vitals
First Contentful Paint: 8.3 s
8.3 sThe first text or image appears after 8.3 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 24.4 s
24.4 sYour largest element takes 24.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “IntelliBids by E-Railspot”.
Speed Index: 17.7 s
17.7 sVisually, the page fills in at 17.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.
7 images without width and height
7 images have no width and height attributes, so the layout jumps as each one loads.
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.
2 checks passed
Total Blocking Time: 100 ms
100 msScripts block the page for only 100 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.009
0.009The layout barely moves while loading (CLS 0.009, good is under 0.1).
Images and page weight
Page weight: 41.7 MB in 159 requests
41.7 MBYour homepage downloads 41.7 MB in 159 requests on a phone: images 39.7 MB (73), stylesheets 839 KiB (24) and scripts 794 KiB (27). Under 2 MB keeps phones on slow connections fast.
11 images over 500 KB
11 images weigh 31.1 MB together. On a phone connection a single image that size takes seconds.
18 images far larger than shown
28.0 MB18 images are downloaded at several times the size a phone draws them, for example prodoBAzj1778614913.jpg at 5,712 px wide, shown at 328 px. Resized copies would save about 28.0 MB.
39 images in older formats
39 images (36.1 MB) 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.
About 11.8 g of CO₂ per visit
11.83 gBy the Sustainable Web Design model, a visit to your homepage emits about 11.83 g of CO₂e: 1419.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
6 text elements with low contrast
6 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 (8 elements)
All page content should be contained by landmarks: 8 elements on the page fail this check, rated moderate by axe-core.
56 links without text
56 visible links have no text or label, so screen readers cannot say where they go.
7 form fields without a label
7 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 66 images in the HTML carry an alt attribute.
49 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
76 links crawlers can't follow
76 links have no real href, so search engines can't follow them.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
202 internal links, 3 external
The homepage links to 202 pages on e-railspot.com and 3 external pages.
8 checks passed
Meta description: 160 characters
Your meta description is 160 characters: “Buy, Sell, Ship, Manage, Track, Monitor, Extend. Our Procurement and Asset Awareness SaaS and Services help businesses …”.
One H1 headline
Your main headline reads: “Launch IntelliBids AI Procurement Assistant”.
Title: 56 characters
Your title is a healthy 56 characters: “Comprehensive Procurement and Asset Awareness solutions.”.
Canonical URL set
The canonical URL is https://e-railspot.com/.
Structured data in place
Structured data found: Organization 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://e-railspot.com/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
No llms.txt
There is no https://e-railspot.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 (823 words), so crawlers that don't run JavaScript still read it.
Other pages
8 pages share a title
https://e-railspot.com/product-spot/rfq_spot/3371, https://e-railspot.com/product-spot/rfq_spot/3235, https://e-railspot.com/product-detail/2601, https://e-railspot.com/product-spot/rfq_spot/2601, https://e-railspot.com/product-detail/2453 and https://e-railspot.com/product-spot/rfq_spot/2453 and 2 others all use the title “IntelliBids by E-Railspot”. Search engines can't tell which page to show for a search, so each competes with the others.
8 pages share a meta description
https://e-railspot.com/product-spot/rfq_spot/3371, https://e-railspot.com/product-spot/rfq_spot/3235, https://e-railspot.com/product-detail/2601, https://e-railspot.com/product-spot/rfq_spot/2601, https://e-railspot.com/product-detail/2453 and https://e-railspot.com/product-spot/rfq_spot/2453 and 2 others use the same meta description. A description written for each page earns more clicks.
9 pages without an H1
https://e-railspot.com/product-spot/deal_spot, https://e-railspot.com/product-spot/product_spot, https://e-railspot.com/product-spot/shipping_spot, https://e-railspot.com/product-spot/rfq_spot, https://e-railspot.com/product-spot/rfq_spot/3371 and https://e-railspot.com/product-spot/rfq_spot/3235 and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.
3 pages slow to respond
https://e-railspot.com/product-detail/2601, https://e-railspot.com/product-detail/2453 and https://e-railspot.com/product-detail/2437 took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 128 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.
Every page has a meta description
All 14 pages that loaded have a meta description.
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
37 small tap targets
37 of 156 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
3 third-party cookies
3 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://data.stbuttons.click/data' from origin 'https://e-railspot.com' has been blocked b…”.
Browser-reported issues
Chrome logged issues while loading the page (“Mixed content”).
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 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 768 words of copy
The homepage carries about 768 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Start Intellibids Chat”.
124 calls to action
The homepage has 124 calls to action, for example “Sign Up”, “Start Intellibids Chat” and “🛒Buy Purchase rail products & equipment”.
1 short form
A short form (2 fields at most) is right on the homepage.
Social proof on the page
Social proof on the homepage: 56 testimonial or review blocks, 56 customer or partner logos and 1 trust badge.
Analytics in place
Analytics detected: Google Tag Manager and LinkedIn Insight.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Tag Manager, LinkedIn Insight and The Trade Desk (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.
4 cookies set on arrival
4Opening the homepage sets 4 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.
20 other companies contacted
Loading the homepage contacts 20 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 e-railspot.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 Tag Manager
- Hosting
- AWS
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 34 issues on e-railspot.com, including 15 speed issues, 2 SEO issues and 1 conversion gap. 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.