Tools & Wizards About Us
idspecial.com screenshot

Report Summary

  • 4

    Performance

    Renders faster than
    20% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 89

    SEO

    Google-friendlier than
    67% of websites

idspecial.com

Instant Ready To Cook Food | Natural, Organic Homemade Food

Page Load Speed

12.8 sec in total

First Response

644 ms

Resources Loaded

11.4 sec

Page Rendered

729 ms

idspecial.com screenshot

About Website

Visit idspecial.com now to see the best up-to-date Idspecial content for India and also check out these interesting facts you probably never knew about idspecial.com

Get Fresh and Natural Ready to Cook Homemade food - Just Like Maa Used to Make ✓100% Natural ✓No preservatives ✓Premium quality ingredients

Visit idspecial.com

Key Findings

We analyzed Idspecial.com page load time and found that the first response time was 644 ms and then it took 12.1 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

idspecial.com performance score

4

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

21/100

10%

LCP (Largest Contentful Paint)

Value8.7 s

1/100

25%

SI (Speed Index)

Value12.9 s

2/100

10%

TBT (Total Blocking Time)

Value6,480 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.635

9/100

15%

TTI (Time to Interactive)

Value18.8 s

3/100

10%

Network Requests Diagram

idspecial.com

644 ms

bootstrap.css

1210 ms

style.css

626 ms

animate.css

633 ms

touchTouch.css

631 ms

Our browser made a total of 121 requests to load all elements on the main page. We found that 40% of them (49 requests) were addressed to the original Idspecial.com, 21% (25 requests) were made to Google.com and 15% (18 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (8.2 sec) belongs to the original domain Idspecial.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (51%)

Content Size

2.4 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Idspecial.com main page is 2.4 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 65% of websites need less resources to load. Javascripts take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 18.9 kB

  • Original 24.4 kB
  • After minification 19.3 kB
  • After compression 5.6 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. This page needs HTML code to be minified as it can gain 5.1 kB, which is 21% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 18.9 kB or 77% of the original size.

Image Optimization

-3%

Potential reduce by 22.5 kB

  • Original 747.8 kB
  • After minification 725.3 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. Idspecial images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 913.9 kB

  • Original 1.3 MB
  • After minification 1.2 MB
  • After compression 393.2 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 913.9 kB or 70% of the original size.

CSS Optimization

-87%

Potential reduce by 260.7 kB

  • Original 299.4 kB
  • After minification 239.5 kB
  • After compression 38.7 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. Idspecial.com needs all CSS files to be minified and compressed as it can save up to 260.7 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 56 (52%)

Requests Now

107

After Optimization

51

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

idspecial.com

idspecial.com

644 ms

bootstrap.css

bootstrap.css

1210 ms

style.css

style.css

626 ms

animate.css

animate.css

633 ms

touchTouch.css

touchTouch.css

631 ms

font-awesome.css

font-awesome.css

648 ms

font-awesome.min.css

font-awesome.min.css

9 ms

validationEngine.jquery.css

validationEngine.jquery.css

650 ms

jquery.js

jquery.js

1864 ms

jquery-migrate-1.2.1.min.js

jquery-migrate-1.2.1.min.js

1243 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

1265 ms

jquery.mobilemenu.js

jquery.mobilemenu.js

1265 ms

jquery.equalheights.js

jquery.equalheights.js

1285 ms

touchTouch.jquery.js

touchTouch.jquery.js

1846 ms

js

js

41 ms

jquery.validationEngine-en.js

jquery.validationEngine-en.js

1860 ms

jquery.validationEngine.js

jquery.validationEngine.js

2192 ms

wow.js

wow.js

1908 ms

device.min.js

device.min.js

1902 ms

jquery.mobile.customized.min.js

jquery.mobile.customized.min.js

2464 ms

gen_validatorv31.js

gen_validatorv31.js

2510 ms

bootstrap.min.js

bootstrap.min.js

2564 ms

tm-scripts.js

tm-scripts.js

2571 ms

css

css

28 ms

css

css

40 ms

maps

maps

91 ms

iD_logo.jpg

iD_logo.jpg

340 ms

BigBasket.jpg

BigBasket.jpg

608 ms

Grofers.jpg

Grofers.jpg

628 ms

Zopnow.jpg

Zopnow.jpg

629 ms

UrDoorStep.jpg

UrDoorStep.jpg

630 ms

BuyerszSpot.jpg

BuyerszSpot.jpg

677 ms

BuyNow.png

BuyNow.png

1032 ms

iD_Products_Home.jpg

iD_Products_Home.jpg

6824 ms

iD_Logo.png

iD_Logo.png

1309 ms

FreshIngredients.jpg

FreshIngredients.jpg

2184 ms

NoPreservatives.jpg

NoPreservatives.jpg

2243 ms

Traditionally.jpg

Traditionally.jpg

2219 ms

RO_Water.jpg

RO_Water.jpg

2552 ms

bg_pic1.jpg

bg_pic1.jpg

8208 ms

BuyNow_B

BuyNow_B

3482 ms

device.min.js

device.min.js

2788 ms

superfish.js

superfish.js

2831 ms

jquery.mousewheel.min.js

jquery.mousewheel.min.js

3115 ms

jquery.simplr.smoothscroll.min.js

jquery.simplr.smoothscroll.min.js

3431 ms

jquery.stellar.js

jquery.stellar.js

3481 ms

jquery.ui.totop.js

jquery.ui.totop.js

3753 ms

GothamRounded-Light.otf

GothamRounded-Light.otf

4021 ms

GothamRounded-Bold.otf

GothamRounded-Bold.otf

5931 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

6 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

5583 ms

embed

embed

559 ms

js

js

104 ms

init_embed.js

init_embed.js

96 ms

common.js

common.js

65 ms

map.js

map.js

98 ms

google4.png

google4.png

111 ms

overlay.js

overlay.js

57 ms

util.js

util.js

105 ms

onion.js

onion.js

103 ms

search_impl.js

search_impl.js

105 ms

stats.js

stats.js

26 ms

openhand_8_8.cur

openhand_8_8.cur

50 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

210 ms

controls.js

controls.js

12 ms

transparent.png

transparent.png

33 ms

css

css

132 ms

entity11.png

entity11.png

102 ms

mapcnt6.png

mapcnt6.png

53 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

42 ms

kh

kh

140 ms

kh

kh

131 ms

tmapctrl.png

tmapctrl.png

57 ms

QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf

QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf

107 ms

RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf

RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf

116 ms

Hgo13k-tfSpn0qi1SFdUfSZ2oysoEQEeKwjgmXLRnTc.ttf

Hgo13k-tfSpn0qi1SFdUfSZ2oysoEQEeKwjgmXLRnTc.ttf

124 ms

d-6IYplOFocCacKzxwXSOCZ2oysoEQEeKwjgmXLRnTc.ttf

d-6IYplOFocCacKzxwXSOCZ2oysoEQEeKwjgmXLRnTc.ttf

142 ms

vt

vt

179 ms

vt

vt

210 ms

vt

vt

145 ms

vt

vt

165 ms

vt

vt

161 ms

vt

vt

142 ms

vt

vt

209 ms

vt

vt

249 ms

vt

vt

246 ms

vt

vt

224 ms

vt

vt

218 ms

vt

vt

291 ms

vt

vt

272 ms

vt

vt

313 ms

vt

vt

292 ms

vt

vt

310 ms

vt

vt

294 ms

vt

vt

378 ms

vt

vt

339 ms

vt

vt

391 ms

vt

vt

371 ms

vt

vt

354 ms

vt

vt

350 ms

AuthenticationService.Authenticate

AuthenticationService.Authenticate

16 ms

gtm.js

gtm.js

73 ms

analytics.js

analytics.js

53 ms

top.png

top.png

583 ms

collect

collect

42 ms

collect

collect

84 ms

conversion_async.js

conversion_async.js

19 ms

fbds.js

fbds.js

102 ms

collect

collect

26 ms

61 ms

22 ms

108 ms

GothamRounded-Light.woff

GothamRounded-Light.woff

617 ms

common.js

common.js

19 ms

util.js

util.js

38 ms

stats.js

stats.js

25 ms

AuthenticationService.Authenticate

AuthenticationService.Authenticate

125 ms

GothamRounded-Light.ttf

GothamRounded-Light.ttf

649 ms

GothamRounded-Light.svg

GothamRounded-Light.svg

644 ms

QuotaService.RecordEvent

QuotaService.RecordEvent

14 ms

23 ms

Accessibility Review

idspecial.com accessibility score

71

Accessibility Issues

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

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

idspecial.com 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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

idspecial.com SEO score

89

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

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 Idspecial.com 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 Idspecial.com 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

idspecial.com

Open Graph description is not detected on the main page of Idspecial. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: