Tools & Wizards About Us
classictenders.in screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 62

    SEO

    Google-friendlier than
    23% of websites

classictenders.in

Page Load Speed

12.2 sec in total

First Response

1.5 sec

Resources Loaded

9.7 sec

Page Rendered

974 ms

classictenders.in screenshot

About Website

Visit classictenders.in now to see the best up-to-date Classictenders content and also check out these interesting facts you probably never knew about classictenders.in

Classic Tender is one of India’s largest tender information service providers for government and private tenders. We offer online GeM portal registration services.

Visit classictenders.in

Key Findings

We analyzed Classictenders.in page load time and found that the first response time was 1.5 sec and then it took 10.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

classictenders.in performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.1 s

1/100

10%

LCP (Largest Contentful Paint)

Value12.1 s

0/100

25%

SI (Speed Index)

Value13.2 s

2/100

10%

TBT (Total Blocking Time)

Value6,280 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.041

99/100

15%

TTI (Time to Interactive)

Value15.6 s

6/100

10%

Network Requests Diagram

www.classictenders.com

1512 ms

js

111 ms

counter.js

74 ms

jquery191.min.js

1416 ms

css

486 ms

Our browser made a total of 67 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Classictenders.in, 19% (13 requests) were made to Embed.tawk.to and 3% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (3.4 sec) relates to the external source Classictenders.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 102.6 kB (23%)

Content Size

455.5 kB

After Optimization

352.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Classictenders.in main page is 455.5 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 55% of websites need less resources to load. Images take 186.4 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 62.1 kB

  • Original 75.3 kB
  • After minification 75.2 kB
  • After compression 13.2 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 62.1 kB or 82% of the original size.

Image Optimization

-3%

Potential reduce by 6.2 kB

  • Original 186.4 kB
  • After minification 180.2 kB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Classictenders images are well optimized though.

JavaScript Optimization

-18%

Potential reduce by 24.3 kB

  • Original 136.9 kB
  • After minification 136.9 kB
  • After compression 112.6 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 24.3 kB or 18% of the original size.

CSS Optimization

-18%

Potential reduce by 10.0 kB

  • Original 56.9 kB
  • After minification 54.9 kB
  • After compression 46.9 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Classictenders.in needs all CSS files to be minified and compressed as it can save up to 10.0 kB or 18% of the original size.

Requests Breakdown

Number of requests can be reduced by 34 (60%)

Requests Now

57

After Optimization

23

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 57 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Classictenders. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

www.classictenders.com

www.classictenders.com

1512 ms

js

js

111 ms

counter.js

counter.js

74 ms

jquery191.min.js

jquery191.min.js

1416 ms

css

css

486 ms

autocomplete-css

autocomplete-css

314 ms

scripts

scripts

1567 ms

_lst_bootstrap.css

_lst_bootstrap.css

1144 ms

_lst_fontawesome.css

_lst_fontawesome.css

947 ms

swiper.min.css

swiper.min.css

1163 ms

_lst_jquery.fancybox.min.css

_lst_jquery.fancybox.min.css

1370 ms

_lst_main.css

_lst_main.css

1176 ms

_lst_responsive.css

_lst_responsive.css

2075 ms

_lst_jquery.min.js

_lst_jquery.min.js

2295 ms

_lst_popper.min.js

_lst_popper.min.js

2139 ms

_lst_bootstrap.min.js

_lst_bootstrap.min.js

2273 ms

swiper.min.js

swiper.min.js

1876 ms

_lst_custom.js

_lst_custom.js

2519 ms

Home-page-scripts

Home-page-scripts

2517 ms

email-decode.min.js

email-decode.min.js

2122 ms

DownloadAPP-scripts

DownloadAPP-scripts

3102 ms

t.php

t.php

125 ms

js

js

39 ms

conversion_async.js

conversion_async.js

61 ms

71 ms

50 ms

1f127netn

1f127netn

215 ms

logo.png

logo.png

1297 ms

date.png

date.png

1370 ms

location-red.png

location-red.png

1581 ms

our-client1.png

our-client1.png

1580 ms

our-client2.png

our-client2.png

1580 ms

our-client3.png

our-client3.png

2035 ms

our-client4.png

our-client4.png

2031 ms

our-client5.png

our-client5.png

2263 ms

location.png

location.png

2313 ms

call.png

call.png

3261 ms

mail.png

mail.png

2474 ms

whatsapp.png

whatsapp.png

2951 ms

facebook.png

facebook.png

2911 ms

youtube.png

youtube.png

3142 ms

instagram.png

instagram.png

2552 ms

twitter.png

twitter.png

3376 ms

banner-img.jpg

banner-img.jpg

3373 ms

fa-solid-900.woff

fa-solid-900.woff

3382 ms

fa-solid-900.woff

fa-solid-900.woff

2704 ms

fa-regular-400.woff

fa-regular-400.woff

3129 ms

fa-regular-400.woff

fa-regular-400.woff

3025 ms

PAJJhLM6sSoWKfWCAAwDAjgbRAAB42mNgYGBkAIIbCZo5IPrmUn0hGA0AO8EFTQAA

PAJJhLM6sSoWKfWCAAwDAjgbRAAB42mNgYGBkAIIbCZo5IPrmUn0hGA0AO8EFTQAA

72 ms

StateLinks

StateLinks

1755 ms

ui-bg_inset-hard_100_fcfdfd_1x100.png

ui-bg_inset-hard_100_fcfdfd_1x100.png

2622 ms

fa-solid-900.ttf

fa-solid-900.ttf

913 ms

fa-regular-400.ttf

fa-regular-400.ttf

229 ms

fa-regular-400.svg

fa-regular-400.svg

889 ms

fa-solid-900.svg

fa-solid-900.svg

895 ms

twk-arr-find-polyfill.js

twk-arr-find-polyfill.js

87 ms

twk-object-values-polyfill.js

twk-object-values-polyfill.js

143 ms

twk-event-polyfill.js

twk-event-polyfill.js

139 ms

twk-entries-polyfill.js

twk-entries-polyfill.js

135 ms

twk-iterator-polyfill.js

twk-iterator-polyfill.js

147 ms

twk-promise-polyfill.js

twk-promise-polyfill.js

138 ms

twk-main.js

twk-main.js

133 ms

twk-vendor.js

twk-vendor.js

233 ms

twk-chunk-vendors.js

twk-chunk-vendors.js

277 ms

twk-chunk-common.js

twk-chunk-common.js

192 ms

twk-runtime.js

twk-runtime.js

203 ms

twk-app.js

twk-app.js

192 ms

Accessibility Review

classictenders.in accessibility score

68

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[role]s are not contained by their required parent element

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

High

Some elements have a [tabindex] value greater than 0

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

classictenders.in best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

classictenders.in SEO score

62

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

robots.txt is not valid

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Classictenders.in can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Classictenders.in main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

classictenders.in

Open Graph data is detected on the main page of Classictenders. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: