Website review, no card needed

blendsteel.com logo

blendsteel.com website review

Visit site (opens in a new tab)Reviewed 24 October 202651 issues · 88 checks

This review found 51 issues worth fixing on blendsteel.com, 24 of them high impact, across 88 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Full-page screenshot of blendsteel.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. blendsteel.com at 2.9 s2.9 s
  2. blendsteel.com at 5.7 s5.7 s
  3. blendsteel.com at 8.6 s8.6 s
  4. blendsteel.com at 11.4 s11.4 s
  5. blendsteel.com at 14.3 s14.3 s
  6. blendsteel.com at 17.1 s17.1 s
  7. blendsteel.com at 20.0 s20.0 s
  8. blendsteel.com at 22.8 s22.8 s

Speed

20 to fix7
  • Reduce unused JavaScript

    39.8 s · 5.4 MB

    About 5.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 39.8 s faster on a phone.

  • Use efficient cache lifetimes

    25.7 s · 17.2 MB

    186 files are served with short cache lifetimes, so returning visitors download them again (17.2 MB).

  • Render-blocking requests

    24.1 s

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

  • Reduce unused CSS

    6.5 s · 955 KiB

    About 955 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 6.5 s faster on a phone.

  • YouTube adds 3.3 s

    3.3 s

    YouTube costs a phone 3.3 s of main-thread work and 7.5 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Improve image delivery

    1.8 s · 1.4 MB

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

  • Font display

    3.0 s

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

  • Minify JavaScript

    1.2 s · 358 KiB

    358 KiB could be saved by minifying JavaScript.

  • Main-thread work: 11.6 s

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

  • Document request latency

    1.0 s · 139 KiB

    The HTML itself could arrive about 1.0 s sooner: redirects, a slow server response or missing compression delay everything after it.

  • Mobile performance score: 7

    7/100

    Your mobile performance score is 7. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • 3,452 HTML elements

    The page has 3,452 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 (YouTube, Google Tag Manager and cad3dviewer.com and others), adding 10.8 MB and 4.3 s of main-thread time.

  • Reduce initial server response time

    975 ms

    Reduce initial server response time. Google estimates savings of 975 ms on a phone.

  • Minify CSS

    600 ms · 117 KiB

    117 KiB could be saved by minifying CSS.

  • cad3dviewer.com adds 383 ms

    383 ms

    cad3dviewer.com costs a phone 383 ms of main-thread work and 1.9 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.

  • Google Tag Manager adds 442 ms

    442 ms

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

  • 20 long tasks on the main thread

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

  • Server response: 1.1 s

    1.1 s

    Your server takes 1.1 s to send the HTML. Google recommends under 600 ms; everything else waits for it.

  • Google Fonts adds 0 ms

    0 ms

    Google Fonts costs a phone 0 ms of main-thread work and 310 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.

  • 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.

Core Web Vitals

7 to fix9
  • First Contentful Paint: 26.2 s

    26.2 s

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

  • Largest Contentful Paint: 87.4 s

    87.4 s

    Your largest element takes 87.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

  • Speed Index: 50.3 s

    50.3 s

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

  • Time to Interactive: 118.9 s

    118.9 s

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

  • Total Blocking Time: 1.9 s

    1.9 s

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

  • Cumulative Layout Shift: 0.468

    0.468

    The layout shifts by 0.468 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • 28 images without width and height

    28 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.

Images and page weight

4 to fix43
  • Page weight: 27.7 MB in 327 requests

    27.7 MB

    Your homepage downloads 27.7 MB in 327 requests on a phone: scripts 12.2 MB (102), media 5.9 MB (9) and images 5.5 MB (100). Under 2 MB keeps phones on slow connections fast.

  • 12 images in older formats

    12 images (1.0 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.

  • 3 images far larger than shown

    380 KiB

    3 images are downloaded at several times the size a phone draws them, for example 100.png at 700 px wide, shown at 100 px. Resized copies would save about 380 KiB.

  • 9 images below the first screen load straight away

    9 images further down the page (561 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 7.9 g of CO₂ per visit

    7.86 g

    By the Sustainable Web Design model, a visit to your homepage emits about 7.86 g of CO₂e: 942.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Accessibility

6 to fixGoogle 8591
  • 15 text elements with low contrast

    15 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Frames without titles

    9 frames have no title, so screen-reader users cannot tell what they contain.

  • All page content should be contained by landmarks (2,588 elements)

    All page content should be contained by landmarks: 2,588 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.

  • 9 links without text

    9 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 (9 elements)

    Alternative text of images should not be repeated as text: 9 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 133 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 44 WCAG 2.2 A/AA and best-practice rules on the phone render: 37 passed and 7 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 9286
  • No structured data

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

  • Meta description is long (604 characters)

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

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 88 internal links, 3 external

    The homepage links to 88 pages on blendsteel.com and 3 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “# Manufacturer of Industrial Valves”.

  • Title: 40 characters

    Your title is a healthy 40 characters: “VALVE MANUFACTURER IN INDIA - Blendsteel”.

  • Canonical URL set

    The canonical URL is https://blendsteel.com/.

  • 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.blendsteel.com/sitemap.xml.

AI search readiness

1 to fix88
  • 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://blendsteel.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 (4,590 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix93
  • 2 pages share a meta description

    https://blendsteel.com/about_us and https://blendsteel.com/Navigation/products use the same meta description. A description written for each page earns more clicks.

  • 1 page without an H1

    https://blendsteel.com/about_us has 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 83 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

4 to fixGoogle 6970
  • 1 broken image

    1 image failed to load on a phone, for example https://blendsteel.com/.

  • 6 small tap targets

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

  • 5 third-party cookies

    5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • 7 low-resolution images

    7 images are served at too low a resolution for sharp phone screens.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix60
  • 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.

  • No social proof

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

  • 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.

  • About 4,356 words of copy

    The homepage carries about 4,356 words of visible text.

3 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Contact us” and “CONTACT US”.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 1 email link.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    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.

  • 4 cookies set on arrival

    4

    Opening 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.

  • 18 other companies contacted

    Loading the homepage contacts 18 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 blendsteel.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 © 2024.

Stack

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 51 issues on blendsteel.com, including 27 speed issues, 4 SEO issues and 2 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25