Your Website Score is
SEO Rank : 19 Website URL: tanda.co Last Updated: 5 months
Success
62% of passed verification steps
Warning
15% of total warning
Errors
23% of total errors, require fast action
Share
Estimation Traffic and Earnings
622
Unique Visits
Daily
1,150
Pages Views
Daily
$4
Income
Daily
17,416
Unique Visits
Monthly
32,775
Pages Views
Monthly
$100
Income
Monthly
201,528
Unique Visits
Yearly
386,400
Pages Views
Yearly
$1,056
Income
Yearly
Desktop
Mobile
Moz Authority Rank
Page Authority
Authority 0%
Domain Authority
Domain Authority 0%
Moz Rank
0.0/10
Bounce Rate
Rate 0%
Meta Data
Charset
Encoding
Great, language/character encoding is specified: UTF-8
Title Tag
68 Characters
TIME & ATTENDANCE SOFTWARE | WORKFORCE SUCCESS SYSTEM | TANDA AU
Meta Description
149 Characters
Cloud workforce management software inc. time & attendance, online rostering, timesheets, pay rates & payroll integration. Try it free today!
Effective URL
20 Characters
https://www.tanda.co
Excerpt
Page content
Time & Attendance Software | Workforce Success System | Tanda AUTime & Attendance Software | Workforce Success System | Tanda AU Tanda Features HOW IT WORKSOverviewEmployee OnboardingRostersEmployee Time Clock AppAward Interpretati...
Google Preview
Your look like this in google search result
TIME & ATTENDANCE SOFTWARE | WORKFORCE SUCCESS SYSTEM |
https://www.tanda.co
Cloud workforce management software inc. time & attendance, online rostering, timesheets, pay rates & payroll integration. Try it free today!
Robots.txt
File Detected
Sitemap.xml
File Detected
Page Size
Code & Text Ratio
Document Size: ~103.04 KB
Code Size: ~74.88 KB
Text Size: ~28.16 KB Ratio: 27.33%
Social Data
Desktop
Properly size images
Potential savings of 397 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
First CPU Idle
3.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/).
JavaScript execution time
0.6 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Avoids enormous network payloads
Total size was 2,615 KiB
Large network payloads cost users real money and are highly correlated with long load times
Includes front-end JavaScript libraries with known security vulnerabilities
9 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
First Meaningful Paint
1.4 s
First Meaningful Paint measures when the primary content of a page is visible
Initial server response time was short
Root document took 40 ms
Keep the server response time for the main document short because all other requests depend on it
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport
Remove unused CSS
Potential savings of 54 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
Total Blocking Time
130 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Avoid an excessive DOM size
1,826 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)
Minimizes main-thread work
1.8 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Avoid large layout shifts
5 elements found
These DOM elements contribute most to the CLS of the page.
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
First Contentful Paint
1.4 s
First Contentful Paint marks the time at which the first text or image is painted
Speed Index
3.3 s
Speed Index shows how quickly the contents of a page are visibly populated
Largest Contentful Paint
4.2 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
Eliminate render-blocking resources
Potential savings of 1,050 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Remove unused JavaScript
Potential savings of 489 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Max Potential First Input Delay
140 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Page load is not fast enough on mobile networks
Interactive on simulated mobile network at 19.4 s
A fast page load over a cellular network ensures a good mobile user experience
Defer offscreen images
Potential savings of 550 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Time to Interactive
4.5 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Minify JavaScript
Potential savings of 3 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Serve static assets with an efficient cache policy
18 resources found
A long cache lifetime can speed up repeat visits to your page
Minimize third-party usage
Third-party code blocked the main thread for 30 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
Avoid chaining critical requests
57 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
Cumulative Layout Shift
0.001
Cumulative Layout Shift measures the movement of visible elements within the viewport
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
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
Keep request counts low and transfer sizes small
160 requests • 2,615 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Serve images in next-gen formats
Potential savings of 496 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
Largest Contentful Paint
17.6 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Remove unused CSS
Potential savings of 81 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
First CPU Idle
14.8 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/).
Minify JavaScript
Potential savings of 3 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Serve static assets with an efficient cache policy
19 resources found
A long cache lifetime can speed up repeat visits to your page
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 images in next-gen formats
Potential savings of 333 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
Avoid chaining critical requests
58 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
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
Reduce the impact of third-party code
Third-party code blocked the main thread for 1,390 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
Keep request counts low and transfer sizes small
161 requests • 2,509 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Max Potential First Input Delay
820 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Tap targets are not sized appropriately
88% 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
First Meaningful Paint
5.3 s
First Meaningful Paint measures when the primary content of a page is visible
Initial server response time was short
Root document took 30 ms
Keep the server response time for the main document short because all other requests depend on it
Total Blocking Time
1,350 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Defer offscreen images
Potential savings of 410 KiB
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 303 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Eliminate render-blocking resources
Potential savings of 3,790 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
First Contentful Paint (3G)
11388 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Page load is not fast enough on mobile networks
Interactive at 17.9 s
A fast page load over a cellular network ensures a good mobile user experience
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 an excessive DOM size
1,784 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)
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
Document uses legible font sizes
100% 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 432 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Avoids enormous network payloads
Total size was 2,509 KiB
Large network payloads cost users real money and are highly correlated with long load times
First Contentful Paint
5.3 s
First Contentful Paint marks the time at which the first text or image is painted
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport
Speed Index
8.5 s
Speed Index shows how quickly the contents of a page are visibly populated
Includes front-end JavaScript libraries with known security vulnerabilities
9 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Estimated Input Latency
330 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
17.9 s
Time to interactive is the amount of time it takes for the page to become fully interactive
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
Warning! Your title is not optimized
Description Website
Congratulations! Your description is optimized
Robots.txt
Congratulations! Your site 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 20 Links | Relationship | HTTP Status |
| Tanda | Internal Link | 200 |
| Overview | Internal Link | 200 |
| Employee Onboarding | Internal Link | 200 |
| Rosters | Internal Link | 200 |
| Employee Time Clock App | Internal Link | 200 |
| Award Interpretation | Internal Link | 200 |
| Leave Management | Internal Link | 200 |
| Key Alerts | Internal Link | 200 |
| Payroll Integration | Internal Link | 301 |
| Tanda Mobile App | Internal Link | 200 |
| Tanda Chat | Internal Link | 200 |
| Shift Feedback | Internal Link | 200 |
| Shift Swapping | Internal Link | 200 |
| Live Wage Tracker™ | Internal Link | 200 |
| Live Insights | Internal Link | 200 |
| Cognitive Payroll™ | Internal Link | 200 |
| Cognitive Rosters® | Internal Link | 200 |
| Predictive Workforce™ | Internal Link | 200 |
| Tanda PaySure | Internal Link | 200 |
| Pricing | Internal Link | 200 |
Alexa Rank
7,518
Local Rank: AU / Users: 55.6% / PageViews: 71.3%277,196
Global RankDomain Available
| Domain (TDL) and Typo | Status |
|---|---|
| tanda.co | Already Registered |
| tanda.us | Already Registered |
| tanda.com | Already Registered |
| tanda.org | Already Registered |
| tanda.net | Already Registered |
| tnda.co | Available Buy Now! |
| vanda.co | Available Buy Now! |
| ganda.co | Available Buy Now! |
Information Server
Response Header
HTTP headers carry information about the client browser, the requested page and the server
HTTP/2 200
server: nginx
date: Fri, 07 Aug 2020 04:44:09 GMT
content-type: text/html; charset=UTF-8
vary: Accept-Encoding
vary: Accept-Encoding
link: ; rel="https://api.w.org/"
link: ; rel=shortlink
x-powered-by: WP Engine
x-cacheable: SHORT
vary: Accept-Encoding,Cookie
cache-control: max-age=600, must-revalidate
x-cache: HIT: 40
x-cache-group: normal
content-encoding: gzip
Click to Add/Show Comments