Website review, no card needed

tendersinfo.com logo

tendersinfo.com website review

Visit site (opens in a new tab)Reviewed 27 October 202625 issues · 68 checks

This review found 25 issues worth fixing on tendersinfo.com, 11 of them high impact, across 68 checks. The most urgent: reduce initial server response time. 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

Real-visitor load time (LCP)75th percentile, phones
4.1 s3.1 sMay 9Oct 243.7 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.3 s
May 16, 20263.4 s
May 23, 20263.5 s
May 30, 20263.6 s
Jun 6, 20263.6 s
Jun 13, 20263.5 s
Jun 20, 20263.7 s
Jun 27, 20263.7 s
Jul 4, 20264.0 s
Jul 11, 20263.8 s
Jul 18, 20263.6 s
Jul 25, 20263.4 s
Aug 1, 20263.4 s
Aug 8, 20263.4 s
Aug 15, 20263.3 s
Aug 22, 20263.3 s
Aug 29, 20263.2 s
Sep 5, 20263.3 s
Sep 12, 20263.3 s
Sep 19, 20263.4 s
Sep 26, 20263.5 s
Oct 3, 20263.5 s
Oct 10, 20263.7 s
Oct 17, 20263.7 s
Oct 24, 20263.7 s
Real-visitor tap response (INP)75th percentile, phones
237 ms208 msMay 9Oct 24211 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026216 ms
May 16, 2026215 ms
May 23, 2026214 ms
May 30, 2026215 ms
Jun 6, 2026217 ms
Jun 13, 2026217 ms
Jun 20, 2026221 ms
Jun 27, 2026220 ms
Jul 4, 2026222 ms
Jul 11, 2026225 ms
Jul 18, 2026227 ms
Jul 25, 2026232 ms
Aug 1, 2026233 ms
Aug 8, 2026234 ms
Aug 15, 2026232 ms
Aug 22, 2026232 ms
Aug 29, 2026231 ms
Sep 5, 2026226 ms
Sep 12, 2026223 ms
Sep 19, 2026222 ms
Sep 26, 2026220 ms
Oct 3, 2026220 ms
Oct 10, 2026220 ms
Oct 17, 2026216 ms
Oct 24, 2026211 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

Full-page screenshot of tendersinfo.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. tendersinfo.com at 2.3 s2.3 s
  2. tendersinfo.com at 4.6 s4.6 s
  3. tendersinfo.com at 6.9 s6.9 s
  4. tendersinfo.com at 9.2 s9.2 s
  5. tendersinfo.com at 11.4 s11.4 s
  6. tendersinfo.com at 13.7 s13.7 s
  7. tendersinfo.com at 16.0 s16.0 s
  8. tendersinfo.com at 18.3 s18.3 s

Speed

8 to fix87
  • Reduce initial server response time

    1.9 s

    Reduce initial server response time. Google estimates savings of 1.9 s on a phone.

  • Document request latency

    1.9 s

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

  • Server response: 2.0 s

    2.0 s

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

  • Mobile performance score: 87

    87/100

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

  • Render-blocking requests

    850 ms

    7 files block the first paint until they finish downloading. Deferring or inlining them could save about 850 ms.

  • Reduce unused JavaScript

    300 ms · 233 KiB

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

  • Google Tag Manager adds 340 ms

    340 ms

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

  • 4 long tasks on the main thread

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (Google Tag Manager, Clarity and Other Google APIs/SDKs and others), adding 502 KiB and 483 ms of main-thread time.

  • Use efficient cache lifetimes

    150 ms · 134 KiB

    23 files are served with short cache lifetimes, so returning visitors download them again (134 KiB).

  • Improve image delivery

    193 KiB

    1 image could be 193 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

    2 KiB

    2 KiB could be saved by minifying JavaScript.

1 checks passed
  • Main-thread work: 1.3 s

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

Core Web Vitals

8 to fix33
  • 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.

  • Real-user FCP: 3.2 s

    3.2 s

    Real visitors see the first content after 3.2 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 2.3 s

    2.3 s

    Real visitors wait 2.3 s for your server to start answering (75th percentile). Good is under 800 ms.

  • Speed Index: 18.5 s

    18.5 s

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

  • Time to Interactive: 7.5 s

    7.5 s

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

  • Real-user LCP: 3.3 s

    3.3 s

    Real visitors wait 3.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 228 ms

    228 ms

    Real visitors wait 228 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • 1 image without width and height

    1 image have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) held steady for real visitors

    -1%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 216 ms to 211 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) got 11% slower for real visitors

    +11%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 3.3 s to 3.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

5 checks passed
  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Total Blocking Time: 155 ms

    155 ms

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

  • Largest Contentful Paint: 2.1 s

    2.1 s

    Your largest element renders in 2.1 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Most Trusted Brand for Tenders, RFPs, eTendering & Procurem…”.

  • First Contentful Paint: 1.2 s

    1.2 s

    The first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0.004

    0.004

    The layout barely moves while loading (CLS 0.004, good is under 0.1).

Images and page weight

100
  • About 0.2 g of CO₂ per visit

    0.22 g

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

1 checks passed
  • Page weight: 809 KiB in 46 requests

    809 KiB

    Your homepage downloads 809 KiB in 46 requests on a phone: scripts 549 KiB (15), images 207 KiB (6) and stylesheets 25 KiB (10). That is a lean page.

Accessibility

1 to fixGoogle 9597
  • 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.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 1 image in the HTML carry an alt attribute.

  • 29 automated accessibility rules passed

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

SEO

3 to fixGoogle 10084
  • Title is long (190 characters)

    Your title is 190 characters, so Google will cut it off around 60: “Latest Tenders Details | Public, Government, Online, Business, Procurement Contracts, Pri…”.

  • Meta description is long (230 characters)

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

  • Structured data has 1 problem

    Structured data found (Organization, Product, WebPage and WebSite) but with 1 problem, for example “Product: no offers (price) block”.

  • 133 internal links, 8 external

    The homepage links to 133 pages on tendersinfo.com and 8 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “Most Trusted Brand for Tenders, RFPs,eTendering & Procurement Bids”.

  • Canonical URL set

    The canonical URL is https://www.tendersinfo.com/.

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

AI search readiness

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

  • Organization data: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

Other pages

1 to fix75
  • 3 linked pages are broken

    Your homepage links to https://www.tendersinfo.com/freetrial_ftnew, https://www.tendersinfo.com/tenders-by-sector.php and https://www.tendersinfo.com/tenders-by-region.php, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 3 pages slow to respond

    https://www.tendersinfo.com/tenders-by-product.php, https://www.tendersinfo.com/global-americas-tenders.php and https://www.tendersinfo.com/global-middle-east-tenders.php took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 93 found) and read each the way a search engine does.

6 checks passed
  • Canonical URLs point to themselves

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

  • Every page has a meta description

    All 10 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 10 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9689
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 502 ()”.

  • 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

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

  • Only about 142 words

    The homepage has only about 142 words of visible text; thin pages give Google and first-time buyers little to go on.

6 checks passed
  • 11 calls to action

    The homepage has 11 calls to action, for example “Subscribe”, “Contact Us” and “Schedule Free Demo”.

  • 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: 4 testimonial or review blocks, a star rating and “Trusted by 10,000+ companies”.

  • Analytics in place

    Analytics detected: Google Tag Manager and Microsoft Clarity.

  • Direct contact links

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

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

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

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 tendersinfo.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 | Microsoft Clarity
Hosting
Sucuri

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 25 issues on tendersinfo.com, including 16 speed issues, 3 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