Tools & Wizards About Us
tin-nsdl.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

tin-nsdl.com

PAN card issuance - online, printing, dispatch

Page Load Speed

6.1 sec in total

First Response

445 ms

Resources Loaded

5.5 sec

Page Rendered

108 ms

tin-nsdl.com screenshot

About Website

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

The Income Tax Department has appointed Protean eGov Technologies Ltd (formerly NSDL e-Governance Infrastructure Ltd) for receiving & processing of PAN applications.

Visit tin-nsdl.com

Key Findings

We analyzed Tin-nsdl.com page load time and found that the first response time was 445 ms and then it took 5.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

tin-nsdl.com performance score

0

Network Requests Diagram

tin-nsdl.com

445 ms

www.tin-nsdl.com

439 ms

www.tin-nsdl.com

1495 ms

nsdl.css

410 ms

sub-menu.css

598 ms

Our browser made a total of 80 requests to load all elements on the main page. We found that 96% of them (77 requests) were addressed to the original Tin-nsdl.com, 4% (3 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Tin-nsdl.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 367.4 kB (53%)

Content Size

695.3 kB

After Optimization

327.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Tin-nsdl.com main page is 695.3 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. 25% of websites need less resources to load. Images take 235.4 kB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 141.2 kB

  • Original 155.7 kB
  • After minification 90.6 kB
  • After compression 14.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 65.1 kB, which is 42% 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 141.2 kB or 91% of the original size.

Image Optimization

-5%

Potential reduce by 12.6 kB

  • Original 235.4 kB
  • After minification 222.8 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. Tin Nsdl images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 122.6 kB

  • Original 192.9 kB
  • After minification 178.4 kB
  • After compression 70.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 122.6 kB or 64% of the original size.

CSS Optimization

-82%

Potential reduce by 91.0 kB

  • Original 111.3 kB
  • After minification 98.8 kB
  • After compression 20.2 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. Tin-nsdl.com needs all CSS files to be minified and compressed as it can save up to 91.0 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 47 (62%)

Requests Now

76

After Optimization

29

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

tin-nsdl.com

tin-nsdl.com

445 ms

www.tin-nsdl.com

www.tin-nsdl.com

439 ms

www.tin-nsdl.com

www.tin-nsdl.com

1495 ms

nsdl.css

nsdl.css

410 ms

sub-menu.css

sub-menu.css

598 ms

preload.js

preload.js

602 ms

setimg.js

setimg.js

603 ms

jscript.js

jscript.js

614 ms

expandcollapse.js

expandcollapse.js

622 ms

accordion.js

accordion.js

623 ms

accordion-home.js

accordion-home.js

793 ms

slide.js

slide.js

601 ms

prototype.js

prototype.js

600 ms

move.js

move.js

627 ms

main_menu.js

main_menu.js

632 ms

dw_event.js

dw_event.js

633 ms

font.js

font.js

792 ms

font-min.gif

font-min.gif

227 ms

font-res.gif

font-res.gif

227 ms

font-max.gif

font-max.gif

231 ms

bookmark-icon.gif

bookmark-icon.gif

244 ms

top-link-div.gif

top-link-div.gif

243 ms

arrow-o.png

arrow-o.png

397 ms

new-icon1.gif

new-icon1.gif

403 ms

bullet.jpg

bullet.jpg

403 ms

icon-login.gif

icon-login.gif

437 ms

login-bt.gif

login-bt.gif

448 ms

spacer.gif

spacer.gif

450 ms

icon-bank.gif

icon-bank.gif

596 ms

icon-cc.gif

icon-cc.gif

600 ms

tin-email2.gif

tin-email2.gif

601 ms

new_icon.gif

new_icon.gif

643 ms

rssymbol-home.jpg

rssymbol-home.jpg

654 ms

home-arrow.gif

home-arrow.gif

656 ms

contactus-tdscpc.jpg

contactus-tdscpc.jpg

793 ms

click-here.gif

click-here.gif

797 ms

ga.js

ga.js

37 ms

background.gif

background.gif

798 ms

top-bg.gif

top-bg.gif

847 ms

menu-bg.gif

menu-bg.gif

844 ms

menu-a.gif

menu-a.gif

845 ms

menu-la.gif

menu-la.gif

975 ms

menu-tl-bg.gif

menu-tl-bg.gif

979 ms

newfeatures.php

newfeatures.php

981 ms

box-bot.gif

box-bot.gif

1027 ms

box-top1.gif

box-top1.gif

1039 ms

tl-bg.gif

tl-bg.gif

1038 ms

box-top2.gif

box-top2.gif

1161 ms

bullet-bg.gif

bullet-bg.gif

1165 ms

cc-bg-top.gif

cc-bg-top.gif

1174 ms

cc-bg-bot.gif

cc-bg-bot.gif

1228 ms

tl-cc-bg.gif

tl-cc-bg.gif

1238 ms

content-top.gif

content-top.gif

1239 ms

__utm.gif

__utm.gif

12 ms

__utm.gif

__utm.gif

25 ms

tab-o.gif

tab-o.gif

1165 ms

tab.gif

tab.gif

1171 ms

tab-bot.gif

tab-bot.gif

1182 ms

tab-top1.gif

tab-top1.gif

1241 ms

tab1.gif

tab1.gif

1239 ms

tab-bot1.gif

tab-bot1.gif

1239 ms

tin-nsdl_btn_bg.jpg

tin-nsdl_btn_bg.jpg

1191 ms

e-payment-Pay-Taxes-Online.gif

e-payment-Pay-Taxes-Online.gif

1194 ms

customer-care-bg.jpg

customer-care-bg.jpg

1204 ms

footer-bg.gif

footer-bg.gif

1240 ms

mootools.js

mootools.js

888 ms

caption.js

caption.js

681 ms

general.css

general.css

780 ms

template.css

template.css

786 ms

nsdl1.css

nsdl1.css

800 ms

news-events-update.gif

news-events-update.gif

210 ms

tl-news-events.gif

tl-news-events.gif

201 ms

index-bullet3.gif

index-bullet3.gif

208 ms

news-botton.gif

news-botton.gif

210 ms

rss-icon.gif

rss-icon.gif

203 ms

news-icon.gif

news-icon.gif

202 ms

speeddown1.gif

speeddown1.gif

399 ms

stopticker1.gif

stopticker1.gif

400 ms

speedup1.gif

speedup1.gif

400 ms

undefined

undefined

210 ms

SEO Factors

tin-nsdl.com SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tin-nsdl.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Tin-nsdl.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

tin-nsdl.com

Open Graph description is not detected on the main page of Tin Nsdl. 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: