Your Website Score is
SEO Rank : 19 Website URL: cellecor.in Last Updated: 2 months
Success
54% of passed verification steps
Warning
23% of total warning
Errors
23% of total errors, require fast action
Share
Estimation Traffic and Earnings
0
Unique Visits
Daily
0
Pages Views
Daily
$0
Income
Daily
0
Unique Visits
Monthly
0
Pages Views
Monthly
$0
Income
Monthly
0
Unique Visits
Yearly
0
Pages Views
Yearly
$0
Income
Yearly
Desktop
Mobile
Moz Authority Rank
Page Authority
Authority 17%
Domain Authority
Domain Authority 9%
Moz Rank
1.7/10
Bounce Rate
Rate 0%
Meta Data
Charset
Encoding
Great, language/character encoding is specified: UTF-8
Title Tag
15 Characters
CELLECOR | HOME
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
Cellecor | Home
...
Meta Keywords
5 Detected
Google Preview
Your look like this in google search result
CELLECOR | HOME
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: ~34.52 KB
Code Size: ~21.21 KB
Text Size: ~13.31 KB Ratio: 38.55%
Social Data
Delicious
Total: 0
Facebook
Total: 3,655
Google
Total: 0
Linkedin
Total: 0
Pinterest
Total: 0
Stumbleupon
Total: 0
Tumblr
Total: 0
Vk
Total: 0
Technologies
PWA - Manifest
Manifest is not valid
Your site don't have valid manifest.json, read more in Web App Manifest
Desktop
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport
Page load is not fast enough on mobile networks
Interactive on simulated mobile network at 19.3 s
A fast page load over a cellular network ensures a good mobile user experience
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
Max Potential First Input Delay
190 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Minify CSS
Potential savings of 5 KiB
Minifying CSS files can reduce network payload sizes
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
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
Cumulative Layout Shift
0.885
Cumulative Layout Shift measures the movement of visible elements within the viewport
Reduce initial server response time
Root document took 710 ms
Keep the server response time for the main document short because all other requests depend on it
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
Links do not have descriptive text
1 link found
Descriptive link text helps search engines understand your content
Minimize third-party usage
Third-party code blocked the main thread for 70 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.0 s
Speed Index shows how quickly the contents of a page are visibly populated
Efficiently encode images
Potential savings of 1,234 KiB
Optimized images load faster and consume less cellular data
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)
First Contentful Paint
1.1 s
First Contentful Paint marks the time at which the first text or image is painted
Keep request counts low and transfer sizes small
117 requests • 4,601 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
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 enormous network payloads
Total size was 4,601 KiB
Large network payloads cost users real money and are highly correlated with long load times
Serve images in next-gen formats
Potential savings of 1,704 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
Time to Interactive
4.3 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Properly size images
Potential savings of 57 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Estimated Input Latency
10 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
Serve static assets with an efficient cache policy
58 resources found
A long cache lifetime can speed up repeat visits to your page
Largest Contentful Paint
5.4 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Total Blocking Time
110 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
First CPU Idle
2.5 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/).
Minimizes main-thread work
1.2 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
JavaScript execution time
0.4 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
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
Avoid large layout shifts
5 elements found
These DOM elements contribute most to the CLS of the page.
Remove unused CSS
Potential savings of 33 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
Avoid long main-thread tasks
3 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Remove unused JavaScript
Potential savings of 416 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
First Meaningful Paint
1.6 s
First Meaningful Paint measures when the primary content of a page is visible
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
Mobile
First Contentful Paint
3.5 s
First Contentful Paint marks the time at which the first text or image is painted
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
Reduce JavaScript execution time
2.9 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
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
Speed Index
11.4 s
Speed Index shows how quickly the contents of a page are visibly populated
Remove unused JavaScript
Potential savings of 418 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Minify JavaScript
Potential savings of 58 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
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)
Serve images in next-gen formats
Potential savings of 1,704 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
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport
First Contentful Paint (3G)
6915 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
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
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
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
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
Estimated Input Latency
400 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
Efficiently encode images
Potential savings of 1,234 KiB
Optimized images load faster and consume less cellular data
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
Largest Contentful Paint
32.8 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Max Potential First Input Delay
910 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Cumulative Layout Shift
2.313
Cumulative Layout Shift measures the movement of visible elements within the viewport
Avoid large layout shifts
5 elements found
These DOM elements contribute most to the CLS of the page.
Serve static assets with an efficient cache policy
58 resources found
A long cache lifetime can speed up repeat visits to your page
Avoid enormous network payloads
Total size was 5,299 KiB
Large network payloads cost users real money and are highly correlated with long load times
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
Minimize main-thread work
7.5 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Page load is not fast enough on mobile networks
Interactive at 23.0 s
A fast page load over a cellular network ensures a good mobile user experience
Keep request counts low and transfer sizes small
106 requests • 5,299 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Eliminate render-blocking resources
Potential savings of 3,180 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Time to Interactive
23.0 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Reduce the impact of third-party code
Third-party code blocked the main thread for 890 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
First Meaningful Paint
4.4 s
First Meaningful Paint measures when the primary content of a page is visible
Links do not have descriptive text
1 link found
Descriptive link text helps search engines understand your content
Reduce initial server response time
Root document took 690 ms
Keep the server response time for the main document short because all other requests depend on it
First CPU Idle
11.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/).
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
Minify CSS
Potential savings of 5 KiB
Minifying CSS files can reduce network payload sizes
Remove unused CSS
Potential savings of 34 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
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
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
0
Local Rank: / Users: / PageViews:
Global Rank
Domain Available
| Domain (TDL) and Typo | Status |
|---|---|
| cellecor.co | Already Registered |
| cellecor.us | Already Registered |
| cellecor.com | Already Registered |
| cellecor.org | Already Registered |
| cellecor.net | Already Registered |
| cllecor.in | Already Registered |
| dellecor.in | Already Registered |
| rellecor.in | Already Registered |
Information Server
Response Header
HTTP headers carry information about the client browser, the requested page and the server
HTTP/2 200
date: Thu, 07 Jan 2021 11:11:37 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
Click to Add/Show Comments