Website review, no card needed

bedrocktyres.com logo

bedrocktyres.com website review

Visit site (opens in a new tab)Reviewed 25 October 202646 issues · 78 checks

This review found 46 issues worth fixing on bedrocktyres.com, 19 of them high impact, across 78 checks. The most urgent: use efficient cache lifetimes. 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 bedrocktyres.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. bedrocktyres.com at 4.2 s4.2 s
  2. bedrocktyres.com at 8.3 s8.3 s
  3. bedrocktyres.com at 12.5 s12.5 s
  4. bedrocktyres.com at 16.6 s16.6 s
  5. bedrocktyres.com at 20.8 s20.8 s
  6. bedrocktyres.com at 25.0 s25.0 s
  7. bedrocktyres.com at 29.1 s29.1 s
  8. bedrocktyres.com at 33.3 s33.3 s

Speed

4 to fix54
  • Use efficient cache lifetimes

    21.2 s · 7.1 MB

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

  • Improve image delivery

    18.3 s · 5.7 MB

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

  • Render-blocking requests

    2.4 s

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

  • Mobile performance score: 54

    54/100

    Your mobile performance score is 54 (desktop: 49). Pages that score under 90 lose visitors before the first paint.

  • 6 third-party services on the page

    6 third-party services load with your homepage (jQuery CDN, GoDaddy and JSDelivr CDN and others), adding 417 KiB and 151 ms of main-thread time.

  • Reduce unused JavaScript

    150 ms · 24 KiB

    About 24 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • Reduce unused CSS

    150 ms · 14 KiB

    About 14 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.

  • Font display

    50 ms

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

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

  • Minify CSS

    3 KiB

    3 KiB could be saved by minifying CSS.

  • Minify JavaScript

    3 KiB

    3 KiB could be saved by minifying JavaScript.

2 checks passed
  • Main-thread work: 0.8 s

    A phone's processor spends 0.8 s on main-thread work while loading, 194 ms of it running JavaScript. That is comfortably low.

  • Server response: 2 ms

    2 ms

    Your server sent the HTML in 2 ms, well inside Google's 600 ms guideline.

Core Web Vitals

6 to fix55
  • Largest Contentful Paint: 29.5 s

    29.5 s

    Your largest element takes 29.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “MOTORCYCLE TYRES RANGE”.

  • Time to Interactive: 30.0 s

    30.0 s

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

  • Speed Index: 9.1 s

    9.1 s

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

  • First Contentful Paint: 2.6 s

    2.6 s

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

  • Cumulative Layout Shift: 0.186

    0.186

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

  • 15 images without width and height

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

1 checks passed
  • Total Blocking Time: 0 ms

    0 ms

    Scripts block the page for only 0 ms while loading. Good is under 200 ms.

Images and page weight

5 to fix18
  • Page weight: 7.5 MB in 73 requests

    7.5 MB

    Your homepage downloads 7.5 MB in 73 requests on a phone: images 7.0 MB (34), fonts 267 KiB (5) and scripts 156 KiB (11). Under 2 MB keeps phones on slow connections fast.

  • 5 images over 500 KB

    5 images weigh 3.1 MB together. On a phone connection a single image that size takes seconds.

  • 9 images far larger than shown

    1.6 MB

    9 images are downloaded at several times the size a phone draws them, for example 686fb5a21c60e_slider-5.jpg at 1,600 px wide, shown at 390 px. Resized copies would save about 1.6 MB.

  • 16 images in older formats

    16 images (4.5 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.

  • 10 images below the first screen load straight away

    10 images further down the page (1.9 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 2.1 g of CO₂ per visit

    2.11 g

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

Accessibility

10 to fixGoogle 7485
  • 5 buttons without a name

    5 buttons have no accessible name, so screen readers announce just “button”.

  • 13 tap targets too small

    13 tap targets are too small or too close together to hit reliably with a finger.

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

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

  • 14 images without alt text

    14 images have no alt text, which hurts accessibility and image search.

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

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

  • 9 links without text

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

1 checks passed
  • 40 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 passed and 9 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

9 to fixGoogle 6460
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • 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 (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No XML sitemap

    No XML sitemap at https://bedrocktyres.com/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

    There is no robots.txt at bedrocktyres.com/robots.txt, the first file search crawlers ask for.

  • 9 links with vague text

    9 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

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

  • 112 internal links, 9 external

    The homepage links to 112 pages on bedrocktyres.com and 9 external pages.

1 checks passed
  • Title: 63 characters

    Your title is a healthy 63 characters: “Bedrock Tyres leading manufacturers & exporters 2 wheeler tyres”.

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://bedrocktyres.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

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

  • Text is in the HTML

    Your server sends the page's text in the HTML (665 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix58
  • 1 linked page is broken

    Your homepage links to https://bedrocktyres.com/page.php, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 12 pages share a title

    https://bedrocktyres.com/sales-enquiries.php, https://bedrocktyres.com/dealership-inquiry.php, https://bedrocktyres.com/feedback.php, https://bedrocktyres.com/page/vision-mission.php, https://bedrocktyres.com/faq.php and https://bedrocktyres.com/catalogue.php and 6 others all use the title “Bedrock Tyres leading manufacturers & exporters 2 wheeler tyres.”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 14 pages without a meta description

    https://bedrocktyres.com/sales-enquiries.php, https://bedrocktyres.com/dealership-inquiry.php, https://bedrocktyres.com/feedback.php, https://bedrocktyres.com/page/vision-mission.php, https://bedrocktyres.com/category.php and https://bedrocktyres.com/subcategory.php and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 14 pages without an H1

    https://bedrocktyres.com/sales-enquiries.php, https://bedrocktyres.com/dealership-inquiry.php, https://bedrocktyres.com/feedback.php, https://bedrocktyres.com/page/vision-mission.php, https://bedrocktyres.com/category.php and https://bedrocktyres.com/subcategory.php and 8 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 19 found) and read each the way a search engine does.

3 checks passed
  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • 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

2 to fixGoogle 9687
  • 7 small tap targets

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

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://www.bedrocktyres.com/fontawesome-all.css' from origin 'https://bedrocktyres.com' h…”.

  • 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

5 to fix42
  • 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 analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • A 8-field form

    Your longest form asks for 8 fields (0 required). Every extra field lowers completion.

  • 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 441 words of copy

    The homepage carries about 441 words of visible text.

1 checks passed
  • 4 calls to action

    The homepage has 4 calls to action, for example “Contact us”, “Enquire Now” and “Apply a Job Now”.

Privacy and tracking

  • 3 cookies set on arrival

    3

    Opening the homepage sets 3 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.

  • 7 other companies contacted

    Loading the homepage contacts 7 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 bedrocktyres.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 © 2025.

Stack

Framework
jQuery

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 46 issues on bedrocktyres.com, including 10 speed issues, 9 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

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