fact.co.in website information.

fact.co.in domain name is registered by .IN top-level domain registry. See the other sites registred in .IN domain zone.

Following name servers are specified for fact.co.in domain:

ns1.nic.in
ns10.nic.in
ns7.nic.in
ns2.nic.in

and probably website fact.co.in is hosted by CLOUDFLARENET - Cloudflare, Inc., US web hosting company. Check the complete list of other most popular websites hosted by CLOUDFLARENET - Cloudflare, Inc., US hosting company.

According to Alexa traffic rank the highest website fact.co.in position was 18266 (in the world). The lowest Alexa rank position was 998594. Now website fact.co.in ranked in Alexa database as number 322853 (in the world).

Website fact.co.in Desktop speed measurement score (68/100) is better than the results of 47.59% of other sites shows that the page desktop performance can be improved.

fact.co.in Mobile usability score (63/100) is better than the results of 9.16% of other sites and shows that the page mobile usability is poor and can be improved.

Mobile speed measurement score of fact.co.in (60/100) is better than the results of 54.7% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

Weekly Rank Report

Date	Rank	Change
Sep-22-2024	322,853	-10,204
Sep-21-2024	312,649	6,270
Sep-20-2024	318,919	-2,796
Sep-19-2024	316,123	4,630
Sep-18-2024	320,753	829
Sep-17-2024	321,582	-5,802
Sep-16-2024	315,780	9,731

fact.co.in Rank History

Alexa can identify the popularity of a website as well as its competitors. It is important for website owners and bloggers to know their Alexa ranking because it shows how many visitors have viewed their web page. It gives them a clear idea of how popular their website is on the internet and the ranking of their competitors.

fact.co.in whois

WHOIS is a query and response protocol that is widely used for querying databases that store the registered users or assignees of an Internet resource, such as a domain name, an IP address block, or an autonomous system, but is also used for a wider range of other information.

fact.co.in server information

Servers Location

IP Address
164.100.60.21

Country
India

Region
Delhi

City
Delhi

fact.co.in desktop page speed rank

Last tested: 2019-09-01

Desktop Speed Medium

68/100

fact.co.in Desktop Speed Test Quick Summary

priority - 32 Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 315.5KiB (50% reduction).

Compressing http://fact.co.in/images/iimg01.jpg could save 100.7KiB (75% reduction).
Compressing http://fact.co.in/images/slideshow/1.jpg could save 15.9KiB (40% reduction).
Compressing http://fact.co.in/images/slideshow/10.jpg could save 15.9KiB (40% reduction).
Compressing http://fact.co.in/images/slideshow/11.jpg could save 15.9KiB (40% reduction).
Compressing http://fact.co.in/images/slideshow/12.jpg could save 15.9KiB (40% reduction).
Compressing http://fact.co.in/images/slideshow/2.jpg could save 15.9KiB (40% reduction).
Compressing http://fact.co.in/images/slideshow/3.jpg could save 15.9KiB (40% reduction).
Compressing http://fact.co.in/images/slideshow/4.jpg could save 15.9KiB (40% reduction).
Compressing http://fact.co.in/images/slideshow/5.jpg could save 15.9KiB (40% reduction).
Compressing http://fact.co.in/images/slideshow/6.jpg could save 15.9KiB (40% reduction).
Compressing http://fact.co.in/images/slideshow/7.jpg could save 15.9KiB (40% reduction).
Compressing http://fact.co.in/images/slideshow/8.jpg could save 15.9KiB (40% reduction).
Compressing http://fact.co.in/images/slideshow/9.jpg could save 15.9KiB (40% reduction).
Compressing http://fact.co.in/images/bg_pattern.jpg could save 13.7KiB (88% reduction).
Compressing http://fact.co.in/images/iimg03.jpg could save 10.2KiB (96% reduction).

priority - 10 Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

http://fact.co.in/css/css.css (expiration not specified)
http://fact.co.in/images/bg_pattern.jpg (expiration not specified)
http://fact.co.in/images/close-button.gif (expiration not specified)
http://fact.co.in/images/iimg01.jpg (expiration not specified)
http://fact.co.in/images/iimg03.jpg (expiration not specified)
http://fact.co.in/images/slideshow/1.jpg (expiration not specified)
http://fact.co.in/images/slideshow/10.jpg (expiration not specified)
http://fact.co.in/images/slideshow/11.jpg (expiration not specified)
http://fact.co.in/images/slideshow/12.jpg (expiration not specified)
http://fact.co.in/images/slideshow/2.jpg (expiration not specified)
http://fact.co.in/images/slideshow/3.jpg (expiration not specified)
http://fact.co.in/images/slideshow/4.jpg (expiration not specified)
http://fact.co.in/images/slideshow/5.jpg (expiration not specified)
http://fact.co.in/images/slideshow/6.jpg (expiration not specified)
http://fact.co.in/images/slideshow/7.jpg (expiration not specified)
http://fact.co.in/images/slideshow/8.jpg (expiration not specified)
http://fact.co.in/images/slideshow/9.jpg (expiration not specified)
http://fact.co.in/js/extlink.js (expiration not specified)
http://fact.co.in/js/fontstyle.js (expiration not specified)
http://fact.co.in/js/jquery-1.2.6.min.js (expiration not specified)

priority - 6 Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 3 blocking script resources and 1 blocking CSS resources. This causes a delay in rendering your page.

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.

Remove render-blocking JavaScript:

http://fact.co.in/js/extlink.js
http://fact.co.in/js/fontstyle.js
http://fact.co.in/js/jquery-1.2.6.min.js

Optimize CSS Delivery of the following:

http://fact.co.in/css/css.css

priority - 0 Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 1.3KiB (15% reduction).

Minifying http://fact.co.in/WebResource.axd?d=3MKLKjyE50RhKU…1&t=636284831271971599 could save 860B (16% reduction) after compression.
Minifying http://fact.co.in/WebResource.axd?d=y0PXi1HPSaCm9T…1&t=636284831271971599 could save 466B (12% reduction) after compression.

priority - 0 Minify CSS

Compacting CSS code can save many bytes of data and speed up download and parse times.

Minify CSS for the following resources to reduce their size by 407B (19% reduction).

Minifying http://fact.co.in/css/css.css could save 407B (19% reduction) after compression.

fact.co.in Desktop Resources

Total Resources	27
Number of Hosts	1
Static Resources	26
JavaScript Resources	5
CSS Resources	1

fact.co.in Desktop Resource Breakdown

fact.co.in mobile page speed rank

Last tested: 2019-08-10

Mobile Speed Bad

60/100

fact.co.in Mobile Speed Test Quick Summary

priority - 32 Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 316.1KiB (50% reduction).

Compressing http://fact.co.in/images/iimg01.jpg could save 100.7KiB (75% reduction).
Compressing http://fact.co.in/images/slideshow/1.jpg could save 16.5KiB (41% reduction).
Compressing http://fact.co.in/images/slideshow/10.jpg could save 15.9KiB (40% reduction).
Compressing http://fact.co.in/images/slideshow/11.jpg could save 15.9KiB (40% reduction).
Compressing http://fact.co.in/images/slideshow/12.jpg could save 15.9KiB (40% reduction).
Compressing http://fact.co.in/images/slideshow/2.jpg could save 15.9KiB (40% reduction).
Compressing http://fact.co.in/images/slideshow/3.jpg could save 15.9KiB (40% reduction).
Compressing http://fact.co.in/images/slideshow/4.jpg could save 15.9KiB (40% reduction).
Compressing http://fact.co.in/images/slideshow/5.jpg could save 15.9KiB (40% reduction).
Compressing http://fact.co.in/images/slideshow/6.jpg could save 15.9KiB (40% reduction).
Compressing http://fact.co.in/images/slideshow/7.jpg could save 15.9KiB (40% reduction).
Compressing http://fact.co.in/images/slideshow/8.jpg could save 15.9KiB (40% reduction).
Compressing http://fact.co.in/images/slideshow/9.jpg could save 15.9KiB (40% reduction).
Compressing http://fact.co.in/images/bg_pattern.jpg could save 13.7KiB (88% reduction).
Compressing http://fact.co.in/images/iimg03.jpg could save 10.2KiB (96% reduction).

priority - 24 Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 3 blocking script resources and 1 blocking CSS resources. This causes a delay in rendering your page.

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.

Remove render-blocking JavaScript:

http://fact.co.in/js/extlink.js
http://fact.co.in/js/fontstyle.js
http://fact.co.in/js/jquery-1.2.6.min.js

Optimize CSS Delivery of the following:

http://fact.co.in/css/css.css

priority - 15 Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

priority - 0 Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 1.3KiB (15% reduction).

priority - 0 Minify CSS

Compacting CSS code can save many bytes of data and speed up download and parse times.

Minify CSS for the following resources to reduce their size by 407B (19% reduction).

Minifying http://fact.co.in/css/css.css could save 407B (19% reduction) after compression.

fact.co.in Mobile Resources

Total Resources	27
Number of Hosts	1
Static Resources	26
JavaScript Resources	5
CSS Resources	1

fact.co.in Mobile Resource Breakdown

fact.co.in mobile page usability

Last tested: 2019-08-10

Mobile Usability Bad

63/100

fact.co.in Mobile Usability Test Quick Summary

priority - 40 Use legible font sizes

The following text on your page renders in a way that may be difficult for some of your visitors to read. Use legible font sizes to provide a better user experience.

The following text fragments have a small font size. Increase the font size to make them more legible.

CAPROLACTAM and 2 others render only 5 pixels tall (12 CSS pixels).

| and 1 others render only 6 pixels tall (16 CSS pixels).

| and 2 others render only 4 pixels tall (10 CSS pixels).

हिंदी and 2 others render only 5 pixels tall (12 CSS pixels).

Units and Ventures and 9 others render only 4 pixels tall (10 CSS pixels).

Right to Information and 6 others render only 5 pixels tall (13 CSS pixels).

FEW Enters int…ritime Sector. renders only 5 pixels tall (13 CSS pixels).

Telephone numbers and 12 others render only 5 pixels tall (12 CSS pixels).

FACT a Governm…armaceuticals. renders only 5 pixels tall (12 CSS pixels).

New renders only 5 pixels tall (13 CSS pixels).

Schedule for D…44 - Ad 7/2019 renders only 5 pixels tall (13 CSS pixels).

Contact Us and 5 others render only 5 pixels tall (12 CSS pixels).

All queries/co…may be sent to and 8 others render only 5 pixels tall (12 CSS pixels).

contact-us(at)factltd.com renders only 5 pixels tall (12 CSS pixels).

priority - 10 Configure the viewport

Your page does not have a viewport specified. This causes mobile devices to render your page as it would appear on a desktop browser, scaling it down to fit on a mobile screen. Configure a viewport to allow your page to render properly on all devices.

Configure a viewport for this page.

priority - 7 Size tap targets appropriately

Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.

The following tap targets are close to other nearby tap targets and may need additional spacing around them.

The tap target <a id="A7" href="fedo/default.aspx" class="linkswhite">FEDO</a> and 2 others are close to other tap targets.

The tap target <a id="A1" href="hindi/default.aspx" class="linksfont">हिंदी</a> and 2 others are close to other tap targets.

The tap target <a href="LinkContent.aspx?lid=1" class="Menu2_1 Menu2_3">About FACT</a> and 1 others are close to other tap targets.

The tap target <a href="Secure/admin/w…newsletter.pdf" class="links">FACT NEWS</a> and 9 others are close to other tap targets.

priority - 3 Size content to viewport

The page content is too wide for the viewport, forcing the user to scroll horizontally. Size the page content to the viewport to provide a better user experience.

The page content is 1,008 CSS pixels wide, but the viewport is only 980 CSS pixels wide. The following elements fall outside the viewport:

The element <a href="javascript:increaseFontSize();" class="linksfont">A [+]</a> falls outside the viewport.
The element <td></td> falls outside the viewport.
The element <td>Useful Facility</td> falls outside the viewport.
The element <td class="h2">What is New...</td> falls outside the viewport.
The element <span class="Verdana12">New Schedule f…Click here...</span> falls outside the viewport.
The element <td class="h2">Right to Information</td> falls outside the viewport.
The element <td>Public Information Officers</td> falls outside the viewport.
The element <td class="h2">Dealership</td> falls outside the viewport.
The element <td>Find Dealer</td> falls outside the viewport.
The element <td class="h2">Useful Links</td> falls outside the viewport.
The element <td>Telephone numbers</td> falls outside the viewport.
The element <td>Dept. of Fertilizers</td> falls outside the viewport.
The element <td>Employees Corner</td> falls outside the viewport.
The element <a href="www.urvarak.co.in" class="links">Fertilizers Monitoring System</a> falls outside the viewport.
The element <p id="footer_para">Sitemap | Te…at)factltd.com</p> falls outside the viewport.

fact.co.in similar domains

Similar domains:

www.fact.com
www.fact.net
www.fact.org
www.fact.info
www.fact.biz
www.fact.us
www.fact.mobi
www.act.co.in
www.fact.co.in
www.cact.co.in
www.fcact.co.in
www.cfact.co.in
www.dact.co.in
www.fdact.co.in
www.dfact.co.in
www.ract.co.in
www.fract.co.in
www.rfact.co.in
www.tact.co.in
www.ftact.co.in
www.tfact.co.in
www.gact.co.in
www.fgact.co.in
www.gfact.co.in
www.vact.co.in
www.fvact.co.in
www.vfact.co.in
www.fct.co.in
www.fqct.co.in
www.faqct.co.in
www.fqact.co.in
www.fwct.co.in
www.fawct.co.in
www.fwact.co.in
www.fsct.co.in
www.fasct.co.in
www.fsact.co.in
www.fzct.co.in
www.fazct.co.in
www.fzact.co.in
www.fat.co.in
www.faxt.co.in
www.facxt.co.in
www.faxct.co.in
www.fadt.co.in
www.facdt.co.in
www.fadct.co.in
www.faft.co.in
www.facft.co.in
www.fafct.co.in
www.favt.co.in
www.facvt.co.in
www.favct.co.in
www.fac.co.in
www.facr.co.in
www.factr.co.in
www.facrt.co.in
www.facf.co.in
www.factf.co.in
www.facg.co.in
www.factg.co.in
www.facgt.co.in
www.facy.co.in
www.facty.co.in
www.facyt.co.in

fact.co.in Ping

Ping is a networking utility tool to test if a particular host is reachable. It is a diagnostic that checks reachability of a host on an Internet Protocol (IP) network. In a computer network, a ping test is a way of sending messages from one host to another. Aside from checking if the host is connected to a network, ping also gives indicators of the reliability and general speed of the connection.

fact.co.in TRACEROUTE

Traceroute is a network diagnostic tool used to track the pathway taken by a packet on an IP network from source to destination. Traceroute also records the time taken for each hop the packet makes during its route to the destination. Traceroute uses ICMP (Internet Control Message Protocol) echo packets with variable time to live values. The response time of each hop is calculated. To guarantee accuracy, each hop is queried multiple times (usually three times) to better measure the response of that particular hop.

FACT.CO.IN FACT - - www.fact.co.in -

fact.co.in website information.

Weekly Rank Report

Advertisement

fact.co.in Rank History

fact.co.in whois

fact.co.in server information

Servers Location

fact.co.in desktop page speed rank

fact.co.in Desktop Speed Test Quick Summary

priority - 32 Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 315.5KiB (50% reduction).

priority - 10 Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

priority - 6 Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 3 blocking script resources and 1 blocking CSS resources. This causes a delay in rendering your page.

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.

Remove render-blocking JavaScript:

Optimize CSS Delivery of the following:

priority - 0 Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 1.3KiB (15% reduction).

priority - 0 Minify CSS

Compacting CSS code can save many bytes of data and speed up download and parse times.

Minify CSS for the following resources to reduce their size by 407B (19% reduction).

fact.co.in Desktop Resources

fact.co.in Desktop Resource Breakdown

fact.co.in mobile page speed rank

fact.co.in Mobile Speed Test Quick Summary

priority - 32 Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 316.1KiB (50% reduction).

priority - 24 Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 3 blocking script resources and 1 blocking CSS resources. This causes a delay in rendering your page.

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.

Remove render-blocking JavaScript:

Optimize CSS Delivery of the following:

priority - 15 Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

priority - 0 Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 1.3KiB (15% reduction).

priority - 0 Minify CSS

Compacting CSS code can save many bytes of data and speed up download and parse times.

Minify CSS for the following resources to reduce their size by 407B (19% reduction).

fact.co.in Mobile Resources

fact.co.in Mobile Resource Breakdown

fact.co.in mobile page usability

fact.co.in Mobile Usability Test Quick Summary

priority - 40 Use legible font sizes

The following text on your page renders in a way that may be difficult for some of your visitors to read. Use legible font sizes to provide a better user experience.

The following text fragments have a small font size. Increase the font size to make them more legible.

priority - 10 Configure the viewport

Your page does not have a viewport specified. This causes mobile devices to render your page as it would appear on a desktop browser, scaling it down to fit on a mobile screen. Configure a viewport to allow your page to render properly on all devices.

Configure a viewport for this page.

priority - 7 Size tap targets appropriately

Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.

The following tap targets are close to other nearby tap targets and may need additional spacing around them.

priority - 3 Size content to viewport

The page content is too wide for the viewport, forcing the user to scroll horizontally. Size the page content to the viewport to provide a better user experience.

The page content is 1,008 CSS pixels wide, but the viewport is only 980 CSS pixels wide. The following elements fall outside the viewport:

fact.co.in similar domains

fact.co.in Ping

fact.co.in TRACEROUTE