Your Website Score is

Similar Ranking

19
SITEAPPRAISAL
siteappraisal.xyz
19
BETGLOW – SPORT PREDICTION
betglow.com
19
BEST BOOKMARKING SERVICE WEBSITE ONLINE | OUTLOOK
domain-seositeoutlook.eu
19
BEST PROJECT MANAGEMENT SOFTWARE | JIPANEL
jipanel.com
19
FIND TOKUNBO AND FOREIGN USED CARS, AUTO PARTS ON CAR MART NIGERIA
carmart.ng
19
AKSES INTERNET ::: W W W . V I N N E T . I D
vinnet.id
19
YEEBIA | FREE CL---IFIED ADS IN NIGERIA | JOBS, RENT, FOR SALE
get99.com

Latest Sites

19
BUSINESS, NEWS, ARCHIVE, LATEST, ARTICLE - MAIN BOOKMARKING
main-news.xyz
46
RANKING UNLIMITED SHARE SEO BOOKMARKING ARTICLE
seounlimited.xyz
19
BUSINESS CONTACT NEXT LEVEL RANKING BOOKMARKING
ranking.contact
19
FEATURE MOBILE PHONE IN DELHI|SMART 4G PHONE DELHI|CELLECOR
cellecor.in
34
FREELANCE WEBSITE DEVELOPER IN DELHI,INDIA | THE CODEBLASTER
thecodeblaster.com
21
BEST LAW COLLEGES IN DELHI NCR | BJMC COURSE IN NOIDA | DME
dme.ac.in
11
TREMAN | ELECTRICAL GOODS MANUFACTURER,SUPPLIER,DEALER IN DELHI
treman.in

19 cellecor.in Last Updated: 3 weeks

Success 54% of passed verification steps
Warning 23% of total warning
Errors 23% of total errors, require fast action

Desktop

Mobile

Performance Desktop Score 35%
Best Practices Desktop Score 71%
SEO Desktop Score 73%
Progressive Web App Desktop Score 26%
Performance Mobile Score 3%
Best Practices Mobile Score 71%
SEO Mobile Score 74%
Progressive Web App Mobile Score 29%
Page Authority Authority 17%
Domain Authority Domain Authority 9%
Moz Rank 1.7/10
Bounce Rate Rate 0%
charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 59 Characters
FEATURE MOBILE PHONE IN DELHI|SMART 4G PHONE DELHI|CELLECOR
Meta Description 230 Characters
Cellecor, as one of the byproducts of Make In India project, presents you with a wide range of Smart 4G phones, Mobile Accessories (wireless earphones & headphones, affordable power banks, bluetooth speakers), Feature Phones, etc.
Effective URL 19 Characters
https://cellecor.in
Excerpt Page content
Feature mobile phone in Delhi|Smart 4G phone Delhi|cellecor ...
Keywords Cloud Density
cellecor8 more3 service3 catobj3 contact3 about3 heights2 rohini2 viewing2 experience2
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
cellecor 8
more 3
service 3
catobj 3
contact 3
about 3
heights 2
rohini 2
viewing 2
experience 2
Google Preview Your look like this in google search result
FEATURE MOBILE PHONE IN DELHI|SMART 4G PHONE DELHI|CELLECOR
https://cellecor.in
Cellecor, as one of the byproducts of Make In India project, presents you with a wide range of Smart 4G phones, Mobile Accessories (wireless earphones
Robots.txt File No Found
Sitemap.xml File Detected
Page Size Code & Text Ratio
Document Size: ~35.36 KB
Code Size: ~21.96 KB
Text Size: ~13.4 KB Ratio: 37.91%

Social Data

Estimation Traffic and Earnings

104
Unique Visits
Daily
192
Pages Views
Daily
$0
Income
Daily
2,912
Unique Visits
Monthly
5,472
Pages Views
Monthly
$0
Income
Monthly
33,696
Unique Visits
Yearly
64,512
Pages Views
Yearly
$0
Income
Yearly

Desktop

Desktop Screenshot
JavaScript execution time 0.7 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
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
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
Avoids large JavaScript libraries with smaller alternatives 0 large libraries found
Large JavaScript libraries can lead to poor performance. Prefer smaller, functionally equivalent libraries to reduce your bundle size
Cumulative Layout Shift 0.662
Cumulative Layout Shift measures the movement of visible elements within the viewport
First Contentful Paint 1.8 s
First Contentful Paint marks the time at which the first text or image is painted
Avoid enormous network payloads Total size was 5,818 KiB
Large network payloads cost users real money and are highly correlated with long load times
Serve static assets with an efficient cache policy 57 resources found
A long cache lifetime can speed up repeat visits to your page
Links do not have descriptive text 1 link found
Descriptive link text helps search engines understand your content
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
Speed Index 5.8 s
Speed Index shows how quickly the contents of a page are visibly populated
Avoid chaining critical requests 60 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
Remove unused JavaScript Potential savings of 841 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Avoids an excessive DOM size 382 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)
Remove unused CSS Potential savings of 83 KiB
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
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
Avoid long main-thread tasks 6 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
First CPU Idle 3.3 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/).
Includes front-end JavaScript libraries with known security vulnerabilities 14 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Avoid serving legacy JavaScript to modern browsers Potential savings of 12 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers
Max Potential First Input Delay 150 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
First Meaningful Paint 2.2 s
First Meaningful Paint measures when the primary content of a page is visible
Reduce initial server response time Root document took 1,290 ms
Keep the server response time for the main document short because all other requests depend on it
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
Largest Contentful Paint 6.1 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Total Blocking Time 130 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Minify CSS Potential savings of 5 KiB
Minifying CSS files can reduce network payload sizes
Minify JavaScript Potential savings of 58 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Keep request counts low and transfer sizes small 115 requests • 5,818 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
User Timing marks and measures 4 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences
Eliminate render-blocking resources Potential savings of 520 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Page load is not fast enough on mobile networks Interactive on simulated mobile network at 27.0 s
A fast page load over a cellular network ensures a good mobile user experience
Minimizes main-thread work 1.4 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Efficiently encode images Potential savings of 1,621 KiB
Optimized images load faster and consume less cellular data
Time to Interactive 6.0 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Serve images in next-gen formats Potential savings of 2,192 KiB
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

Mobile Screenshot
Remove unused CSS Potential savings of 83 KiB
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
Speed Index 18.9 s
Speed Index shows how quickly the contents of a page are visibly populated
Total Blocking Time 1,340 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
User Timing marks and measures 4 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences
Keep request counts low and transfer sizes small 115 requests • 5,816 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Avoids an excessive DOM size 380 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)
Includes front-end JavaScript libraries with known security vulnerabilities 14 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Estimated Input Latency 230 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
Time to Interactive 25.1 s
Time to interactive is the amount of time it takes for the page to become fully 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
First Meaningful Paint 8.0 s
First Meaningful Paint measures when the primary content of a page is visible
Serve images in next-gen formats Potential savings of 1,656 KiB
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
Links do not have descriptive text 1 link found
Descriptive link text helps search engines understand your content
Minify JavaScript Potential savings of 58 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Eliminate render-blocking resources Potential savings of 1,200 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Avoid serving legacy JavaScript to modern browsers Potential savings of 12 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers
Document uses legible font sizes 99.83% 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
Remove unused JavaScript Potential savings of 852 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Avoids large JavaScript libraries with smaller alternatives 0 large libraries found
Large JavaScript libraries can lead to poor performance. Prefer smaller, functionally equivalent libraries to reduce your bundle size
Efficiently encode images Potential savings of 1,217 KiB
Optimized images load faster and consume less cellular data
Minimize main-thread work 6.4 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Max Potential First Input Delay 690 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
First CPU Idle 14.9 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/).
Avoid chaining critical requests 60 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
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 at 25.1 s
A fast page load over a cellular network ensures a good mobile user experience
Reduce initial server response time Root document took 1,280 ms
Keep the server response time for the main document short because all other requests depend on it
First Contentful Paint (3G) 15494 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Reduce JavaScript execution time 3.7 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Serve static assets with an efficient cache policy 57 resources found
A long cache lifetime can speed up repeat visits to your page
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
Cumulative Layout Shift 1.479
Cumulative Layout Shift measures the movement of visible elements within the viewport
Minify CSS Potential savings of 5 KiB
Minifying CSS files can reduce network payload sizes
Largest Contentful Paint 33.6 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Avoid enormous network payloads Total size was 5,816 KiB
Large network payloads cost users real money and are highly correlated with long load times
Avoid long main-thread tasks 20 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
First Contentful Paint 7.5 s
First Contentful Paint marks the time at which the first text or image is painted
Tap targets are not sized appropriately 70% 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
Reduce the impact of third-party code Third-party code blocked the main thread for 1,490 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

Speed And Optimization Tips

Website speed has a huge impact on performance, affecting user experience, conversion rates and even rankings. ‪‬‬By reducing page load-times, users are less likely to get distracted and the search engines are more likely to reward you by ranking you
Title Website
Congratulations! Your title is optimized
Description Website
Warning! Your description is not optimized
Robots.txt
Warning! Your site not have a robots.txt file
Sitemap.xml
Congratulations! We've found a sitemap file for your website
SSL Secure
Congratulations! Your site have Support to HTTPS
Headings
Congratulations! You are using your H1 and H2 tags in your site
Blacklist
Congratulations! Your site is not listed in a blacklist
W3C Validator
Warning! Your site have errors W3C
Accelerated Mobile Pages (AMP)
Warning! Your site not have AMP Version
Domain Authority
Warning! Domain Authority of your website is slow. It is good to have domain authority more than 25.
GZIP Compress
Warning! Your site not is compressed, this can make slower response for the visitors
Favicon
Congratulations! Your website appears to have a favicon.
Broken Links
Congratulations! You not have broken links View links

Alexa Rank

3,164,840

Global Rank

3,164,840

Global
Traffic
Search

Domain Available

Domain (TDL) and Typo Status
cellecor.co Available Buy Now!
cellecor.us Available Buy Now!
cellecor.com Already Registered
cellecor.org Available Buy Now!
cellecor.net Available Buy Now!
cllecor.in Available Buy Now!
dellecor.in Available Buy Now!
rellecor.in Available Buy Now!

Information Server

Response Header HTTP headers carry information about the client browser, the requested page and the server
HTTP/2 200 
date: Mon, 15 Feb 2021 12:43:11 GMT
server: Apache
x-powered-by: PHP/7.1.33
content-security-policy: upgrade-insecure-requests
strict-transport-security: max-age=63072000; includeSubDomains
vary: User-Agent
x-xss-protection: 1; mode=block
x-frame-options: SAMEORIGIN
x-content-type-options: nosniff
content-security-policy: ...
referrer-policy: same-origin
feature-policy: geolocation 'self'; vibrate 'none'
content-type: text/html; charset=UTF-8
DNS Records DNS Resource Records associated with a hostname
View DNS Records