Freecharge.in - SEO Checker

Your Website Score is

Similar Ranking

PROGRAMMING & ENGINEERING QUESTIONS & ANSWERS - SANFOUNDRY

sanfoundry.com

faire.com

SHARE VIDEOS 動画のシェアでお金稼ぎできるサイト

share-videos.se

ROLLERCOIN – ONLINE BITCOIN MINING SIMULATOR GAME

rollercoin.com

ژاکت | مارکت وردپرس | قالب وردپرس | پوسته وردپرس

zhaket.com

GARENA

garena.com

VERIZON MEDIA

verizonmedia.com

Latest Sites

GOLIKE

tiktok.golike.one

ACUITY FUNDING

acuityfunding.com

sharenow126.com

MASUK

gm066.com

恭喜，站点创建成功！

51278.cc

m.fun8899jk.com

JOBIFY

jobify2u.com

Top Technologies

Nginx

Web Servers

PHP

Programming Languages

Google Tag Manager

Tag Managers

Google Font API

Font Scripts

CloudFlare

CDN

jQuery

JavaScript Frameworks

Apache

Web Servers

Font Awesome

Font Scripts

WordPress

CMS

Twitter Bootstrap

Web Frameworks

21 freecharge.in Last Updated: 1 year

Success 47% of passed verification steps

Warning 30% of total warning

Errors 23% of total errors, require fast action

Mobile

Performance Desktop Score 77%

Best Practices Desktop Score 69%

SEO Desktop Score 82%

Progressive Web App Desktop Score 19%

Performance Mobile Score 85%

Best Practices Mobile Score 69%

SEO Mobile Score 83%

Progressive Web App Mobile Score 63%

Page Authority Authority 0%

Domain Authority Domain Authority 0%

Moz Rank 0.0/10

Bounce Rate Rate 0%

Title Tag 105 Characters

ONLINE RECHARGE ON FREECHARGE | FAST & EASY RECHARGE FOR PREPAID MOBILE, POSTPAID MOBILE, DATACARD & DTH.

Meta Description 171 Characters

FreeCharge - The Simplest & Fastest way to do a Online Recharge for Prepaid Mobile, Postpaid Bill, Datacard & DTH. Get exclusive rewards for Online Recharge on FreeCharge.

Effective URL 25 Characters

https://www.freecharge.in

Excerpt Page content

Online Recharge on FreeCharge | Fast & Easy Recharge for Prepaid Mobile, Postpaid Mobile, Datacard & DTH.

Meta Keywords 6 Detected

Online recharge Mobile recharge Online mobile recharge Free recharge Easy Recharge Prepaid Recharge

Google Preview Your look like this in google search result

ONLINE RECHARGE ON FREECHARGE | FAST & EASY RECHARGE FOR PRE

https://www.freecharge.in

FreeCharge - The Simplest & Fastest way to do a Online Recharge for Prepaid Mobile, Postpaid Bill, Datacard & DTH. Get exclusive rewards for Online Re

Robots.txt File Detected

http://freecharge.in/robots.txt

Sitemap.xml File Detected

http://freecharge.in/sitemap.xml

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

Updated: 2018-10-10 / 2 years

Create on: 2009-10-10 / 11 years

Expires on: 2019-10-10 / 15 months 25 days

Net4India ,IN

Registrar URL: http://www.net4.in

Nameservers

NS-175.AWSDNS-21.COM

NS-1592.AWSDNS-07.CO.UK

NS-882.AWSDNS-46.NET

NS-1418.AWSDNS-49.ORG

Page Size Code & Text Ratio

Document Size: ~15.47 KB

Code Size: ~2.78 KB

Text Size: ~12.69 KB Ratio: 82.00%

Estimation Traffic and Earnings

Only Registered Users

Sign up for see all features and reviews about this site

Technologies

PWA - Manifest

Freecharge

The web app manifest is a simple JSON file that gives you, the developer, the ability to control how your app appears to the user in areas where they would expect to see apps (for example, a mobile device's home screen)

Param name

Freecharge

Param gcm_sender_id

811449299901

Manifest is not valid

Your manifest are missing some important params, read more in Web App Manifest

Desktop

Reduce server response times (TTFB) Root document took 1,440 ms

Time To First Byte identifies the time at which your server sends a response

Eliminate render-blocking resources Potential savings of 210 ms

Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles

Enable text compression Potential savings of 112 KB

Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes

Efficiently encode images Potential savings of 97 KB

Optimized images load faster and consume less cellular data

Minimize third-party usage Third-party code blocked the main thread for 0 ms

Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading

Total Blocking Time 120 ms

Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.

JavaScript execution time 0.8 s

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this

Defer offscreen images Potential savings of 219 KB

Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive

Server Backend Latencies 0 ms

Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance

Properly size images Potential savings of 879 KB

Serve images that are appropriately-sized to save cellular data and improve load time

Speed Index 2.3 s

Speed Index shows how quickly the contents of a page are visibly populated

First CPU Idle 2.2 s

First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle).

Avoids enormous network payloads Total size was 2,424 KB

Large network payloads cost users real money and are highly correlated with long load times

Minimizes main-thread work 1.6 s

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this

First Contentful Paint 1.2 s

First Contentful Paint marks the time at which the first text or image is painted

Includes front-end JavaScript libraries with known security vulnerabilities 4 vulnerabilities detected

Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers

Avoid chaining critical requests 13 chains found

The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load

Avoids an excessive DOM size 408 elements

A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow)

First Meaningful Paint 1.3 s

First Meaningful Paint measures when the primary content of a page is visible

Keep request counts low and transfer sizes small 106 requests • 2,424 KB

To set budgets for the quantity and size of page resources, add a budget.json file

Serve static assets with an efficient cache policy 22 resources found

A long cache lifetime can speed up repeat visits to your page

Max Potential First Input Delay 130 ms

The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task

Time to Interactive 2.3 s

Time to interactive is the amount of time it takes for the page to become fully interactive

Network Round Trip Times 0 ms

Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance

Page load is not fast enough on mobile networks Interactive on simulated mobile network at 10.4 s

A fast page load over a cellular network ensures a good mobile user experience

Estimated Input Latency 20 ms

Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy

Remove unused CSS Potential savings of 25 KB

Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity

Serve images in next-gen formats Potential savings of 814 KB

Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption

Mobile

Serve images in next-gen formats Potential savings of 403 KB

Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption

Reduce server response times (TTFB) Root document took 1,000 ms

Time To First Byte identifies the time at which your server sends a response

Eliminate render-blocking resources Potential savings of 150 ms

Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles

Efficiently encode images Potential savings of 239 KB

Optimized images load faster and consume less cellular data

Minimize third-party usage Third-party code blocked the main thread for 130 ms

Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading

Total Blocking Time 190 ms

Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.

JavaScript execution time 0.8 s

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this

Server Backend Latencies 0 ms

Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance

Defer offscreen images Potential savings of 84 KB

Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive

Properly size images Potential savings of 294 KB

Serve images that are appropriately-sized to save cellular data and improve load time

Speed Index 3.5 s

Speed Index shows how quickly the contents of a page are visibly populated

First CPU Idle 4.2 s

First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle).

Avoids enormous network payloads Total size was 820 KB

Large network payloads cost users real money and are highly correlated with long load times

Minimizes main-thread work 1.9 s

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this

First Contentful Paint 2.3 s

First Contentful Paint marks the time at which the first text or image is painted

Avoid chaining critical requests 15 chains found

Avoids an excessive DOM size 335 elements

First Meaningful Paint 2.3 s

First Meaningful Paint measures when the primary content of a page is visible

Keep request counts low and transfer sizes small 67 requests • 820 KB

To set budgets for the quantity and size of page resources, add a budget.json file

Serve static assets with an efficient cache policy 24 resources found

A long cache lifetime can speed up repeat visits to your page

Max Potential First Input Delay 120 ms

The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task

Time to Interactive 4.8 s

Time to interactive is the amount of time it takes for the page to become fully interactive

Network Round Trip Times 0 ms

Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance

Estimated Input Latency 20 ms

First Contentful Paint (3G) 4674 ms

First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network

Tap targets are not sized appropriately 90% appropriately sized tap targets

Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements

Document doesn't use legible font sizes 39.71% legible text

Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px

Speed And Optimization Tips

Only Registered Users

Sign up for see all features and reviews about this site

Alexa Rank

0

Local Rank: / Users: / PageViews:

Global Rank

Information Server

Response Header HTTP headers carry information about the client browser, the requested page and the server

HTTP/1.1 200 OK
Content-Type: text/html; charset=utf-8
X-Powered-By: Express
ETag: W/"TsgVAfFLpORyRyVG5UjHaQ=="
Vary: Accept-Encoding
Content-Encoding: gzip
Expires: Fri, 13 Dec 2019 20:16:29 GMT
Cache-Control: max-age=0, no-cache, no-store
Pragma: no-cache
Date: Fri, 13 Dec 2019 20:16:29 GMT
Content-Length: 20
Connection: keep-alive
Strict-Transport-Security: max-age=31536000 ; includeSubDomains
X-Content-Type-Options: nosniff
X-Frame-Options: sameorigin
X-XSS-Protection: 1

DNS Records DNS Resource Records associated with a hostname

View DNS Records

Type	Name	Value	Class	TTL
A	freecharge.in	13.232.73.101	IN	11
A	freecharge.in	13.234.176.8	IN	11
NS	freecharge.in	ns-175.awsdns-21.com	IN	33112
NS	freecharge.in	ns-1592.awsdns-07.co.uk	IN	33112
NS	freecharge.in	ns-1418.awsdns-49.org	IN	33112
NS	freecharge.in	ns-882.awsdns-46.net	IN	33112
MX	freecharge.in	alt2.aspmx.l.google.com	IN	3600
MX	freecharge.in	alt3.aspmx.l.google.com	IN	3600
MX	freecharge.in	alt4.aspmx.l.google.com	IN	3600
MX	freecharge.in	aspmx.l.google.com	IN	3600
MX	freecharge.in	alt1.aspmx.l.google.com	IN	3600
TXT	freecharge.in	v=spf1 ip4:180.179.32.211 ip4:124.153.83.24 include:amazonses.com include:_spf.google.com ~all	IN	300
TXT	freecharge.in	_globalsign-domain-verification=x0HcJFdlnJIBIcjNR0x88L2IgmzxyUmMEHXzrGicUi	IN	300
TXT	freecharge.in	google-site-verification=EMrtiyMLfwzcdC74uVzxeME_VKzSciaqTiLBgKvqJbc	IN	300
TXT	freecharge.in	google-site-verification=TuoVQnnRDbtUCnUHRfNqx66n9aHELbHXE8Cztg60DfA	IN	300
AAAA	freecharge.in	2406:da00:a000::dea:b008	IN	11
AAAA	freecharge.in	2406:da00:a000::de8:4965	IN	11

Your Website Score is

Similar Ranking

Latest Sites

Top Technologies

21 freecharge.in Last Updated: 1 year

Desktop

Mobile

Estimation Traffic and Earnings

Sign up for see all features and reviews about this site

Technologies

Express

Google Tag Manager

Node js

PWA - Manifest

Desktop

Mobile

Speed And Optimization Tips

Sign up for see all features and reviews about this site

Alexa Rank

0

Information Server

Comments