Your Website Score is

Similar Ranking

19
SITEAPPRAISAL
siteappraisal.xyz
19
FEATURE MOBILE PHONE IN DELHI|SMART 4G PHONE DELHI|CELLECOR
cellecor.in
19
BEST LAW COLLEGES IN DELHI NCR | BJMC COURSE IN NOIDA | DME
dme.ac.in
19
خانه | فرآیند پروژه انجام پروژه مهندسی - انجام پروژه مهندسی شیمی
process-project.com
19
DIGITAL MARKETING TRAINING AGENCY BENIN CITY EDO STATE NIGERIA
digitalmarketingtrainingagency.com
19
BEST PUBLIC SCHOOL IN NORTH DELHI|TOP SCHOOL IN NORTH DELHI
matasukhdevischool.com
19
HEALTH MONITORING BAND IN INDIA | HEALTH CARE BAND IN INDIA | TRES CARE
tres.in

Latest Sites

46
TEKSERVNG. - TECHNOLOGY INFORMATION STRAIGHT TO YOUR SCREEN
tekservng.com
19
PROJECT 60 – PROJECT 60 TALENT HUNT
project60.com.ng
51
ABEGPLAY - DISCOVER THE BEST ENTERTAINMENT NEWS, MOVIES, MUSIC AND VIDEOS FROM AROUND THE WORLD AND EVEN YOUR OWN AREA.
abegplay.com.ng
14
GK HAIR – ОФИЦИАЛЬНЫЙ ИНТЕРНЕТ-МАГАЗИН GLOBAL KERATIN (ГЛОБАЛ КЕРАТИН) В РОССИИ
globalkeratin.ru
23
BLOGEARNS
blogearns.com
38
IRSAH INDESIGNS BLOG
blog.irsah.com
5
VISITOR ANTI-ROBOT VALIDATION
premiumdigitalmarketing.ng

19 cellecor.in Last Updated: 10 months

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

Desktop

Mobile

Performance Desktop Score 41%
Best Practices Desktop Score 73%
SEO Desktop Score 82%
Progressive Web App Desktop Score 36%
Performance Mobile Score 7%
Best Practices Mobile Score 73%
SEO Mobile Score 82%
Progressive Web App Mobile Score 42%
Page Authority Authority 0%
Domain Authority Domain Authority 0%
Moz Rank 0.0/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 ...
Meta Keywords 5 Detected
Smart 4G phones Mobile Accessories (wireless earphones & headphones affordable power banks bluetooth speakers) Feature Phones
Keywords Cloud Density
cellecor7 service3 catobj3 contact3 experience2 plaza2 hotel2 delhi2 info2 matallic2
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
cellecor 7
service 3
catobj 3
contact 3
experience 2
plaza 2
hotel 2
delhi 2
info 2
matallic 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
http://cellecor.in/robots.txt
Sitemap.xml File Detected
http://cellecor.in/sitemap.xml
Page Size Code & Text Ratio
Document Size: ~33.18 KB
Code Size: ~21.26 KB
Text Size: ~11.92 KB Ratio: 35.93%

Social Data

Only Registered Users

Sign up for see all features and reviews about this site

Login

Estimation Traffic and Earnings

145
Unique Visits
Daily
268
Pages Views
Daily
$0
Income
Daily
4,060
Unique Visits
Monthly
7,638
Pages Views
Monthly
$0
Income
Monthly
46,980
Unique Visits
Yearly
90,048
Pages Views
Yearly
$0
Income
Yearly

Desktop

Desktop Screenshot
Preload Largest Contentful Paint image Potential savings of 190 ms
Preload the image used by the LCP element in order to improve your LCP time
Minify JavaScript Potential savings of 58 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
First Meaningful Paint 1.7 s
First Meaningful Paint measures when the primary content of a page is visible
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Avoids an excessive DOM size 366 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)
Web app manifest or service worker do not meet the installability requirements 1 reason
Service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement
Avoid long main-thread tasks 7 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Efficiently encode images Potential savings of 1,217 KiB
Optimized images load faster and consume less cellular data
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
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,821 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
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 non-composited animations 1 animated element found
Animations which are not composited can be janky and increase CLS
Serve static assets with an efficient cache policy 57 resources found
A long cache lifetime can speed up repeat visits to your page
Minimize main-thread work 2.3 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.5 s
First Contentful Paint marks the time at which the first text or image is painted
Total Blocking Time 200 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
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
Reduce initial server response time Root document took 950 ms
Keep the server response time for the main document short because all other requests depend on it
Minify CSS Potential savings of 5 KiB
Minifying CSS files can reduce network payload sizes
Avoid enormous network payloads Total size was 5,821 KiB
Large network payloads cost users real money and are highly correlated with long load times
Time to Interactive 4.1 s
Time to interactive is the amount of time it takes for the page to become fully interactive
First CPU Idle 3.0 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/).
Minimize third-party usage Third-party code blocked the main thread for 200 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 Index 4.7 s
Speed Index shows how quickly the contents of a page are visibly populated
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
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
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
Remove unused JavaScript Potential savings of 858 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Estimated Input Latency 40 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 4.7 s
Largest Contentful Paint marks the time at which the largest text or image is painted
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
Cumulative Layout Shift 1.809
Cumulative Layout Shift measures the movement of visible elements within the viewport
Eliminate render-blocking resources Potential savings of 120 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Avoid chaining critical requests 59 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
Max Potential First Input Delay 230 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task

Mobile

Mobile Screenshot
Speed Index 15.0 s
Speed Index shows how quickly the contents of a page are visibly populated
Serve images in next-gen formats Potential savings of 1,726 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
Estimated Input Latency 300 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
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 Contentful Paint (3G) 15695 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Efficiently encode images Potential savings of 1,217 KiB
Optimized images load faster and consume less cellular data
First Contentful Paint 7.1 s
First Contentful Paint marks the time at which the first text or image is painted
Largest Contentful Paint 17.0 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Preload Largest Contentful Paint image Potential savings of 480 ms
Preload the image used by the LCP element in order to improve your LCP time
Avoid chaining critical requests 59 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 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
Remove unused JavaScript Potential savings of 860 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
First Meaningful Paint 7.4 s
First Meaningful Paint measures when the primary content of a page is visible
Web app manifest or service worker do not meet the installability requirements 1 reason
Service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement
Max Potential First Input Delay 680 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
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
Total Blocking Time 1,000 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Reduce the impact of third-party code Third-party code blocked the main thread for 1,260 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
Minimize main-thread work 7.0 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Cumulative Layout Shift 1.214
Cumulative Layout Shift measures the movement of visible elements within the viewport
Avoid long main-thread tasks 16 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Avoids an excessive DOM size 364 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
Minify JavaScript Potential savings of 58 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Reduce JavaScript execution time 3.3 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Keep request counts low and transfer sizes small 123 requests • 4,767 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Time to Interactive 19.0 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Serve static assets with an efficient cache policy 57 resources found
A long cache lifetime can speed up repeat visits to your page
Reduce initial server response time Root document took 900 ms
Keep the server response time for the main document short because all other requests depend on it
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
First CPU Idle 7.4 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/).
Tap targets are not sized appropriately 68% 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
Avoid enormous network payloads Total size was 4,767 KiB
Large network payloads cost users real money and are highly correlated with long load times
Document uses legible font sizes 99.52% 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
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
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Avoid non-composited animations 1 animated element found
Animations which are not composited can be janky and increase CLS
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
Eliminate render-blocking resources Potential savings of 750 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Minify CSS Potential savings of 5 KiB
Minifying CSS files can reduce network payload sizes

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
First 6 Links Relationship HTTP Status
http://cellecor.in/index.php Internal Link 301
About Internal Link 301
Service Internal Link 301
{{CatObj.name}} Internal Link 301
Contact Internal Link 301
E-WASTE MANAGEMENT Internal Link 301

Alexa Rank

2,016,534

Global Rank

2,016,534

Global
Traffic
Search

Domain Available

Only Registered Users

Sign up for see all features and reviews about this site

Login

Information Server

Response Header HTTP headers carry information about the client browser, the requested page and the server 
HTTP/2 200 
date: Fri, 19 Mar 2021 11:23:59 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
Type Name Value Class TTL
A cellecor.in 166.62.27.181 IN 10668
NS cellecor.in ns21.domaincontrol.com IN 3452
NS cellecor.in ns22.domaincontrol.com IN 3452
MX cellecor.in mail.cellecor.in IN 3600
TXT cellecor.in v=spf1 a mx ptr include:secureserver.net ~all IN 3600

About Us

SiteAppraisal is an online Websites calculator, which helps individuals and Website owners identify pitfalls of their websites and their competitor to aid them be a step ahead of their competitors. To use SiteAppraisal App, you should add the domain of the website e.g SiteAppraisal.com and click on the review button.

Contact Info

SiteAppraisal

Follow Us

Copyright 2021
Languages | English