Your Website Score is
SEO Rank : 34 Website URL: kenzato.uk Last Updated: 3 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
1,501
Unique Visits
Daily
2,776
Pages Views
Daily
$6
Income
Daily
42,028
Unique Visits
Monthly
79,116
Pages Views
Monthly
$150
Income
Monthly
486,324
Unique Visits
Yearly
932,736
Pages Views
Yearly
$1,584
Income
Yearly
Desktop
Mobile
Moz Authority Rank
Page Authority
Authority 36%
Domain Authority
Domain Authority 24%
Moz Rank
3.6/10
Bounce Rate
Rate 0%
Meta Data
Charset
Encoding
Great, language/character encoding is specified: UTF-8
Title Tag
14 Characters
KENZATO'S BLOG
Meta Description
0 Characters
NO DATA
Effective URL
18 Characters
https://kenzato.uk
Excerpt
Page content
Kenzato's blog
Kenzato's blog
Home
About
Welcome
Enjoy your stay
15th December 2018
Playhome Translation reupload attempt 2
https://mega.nz/#!jU5VUYrC!lB...
Google Preview
Your look like this in google search result
KENZATO'S BLOG
https://kenzato.uk
Kenzato's blog
Kenzato's blog
Home
About
Welcome
Enjoy your stay
15th December 2018
Playhome Translation reupload attempt 2
https://mega.nz/#!jU5VUYrC!lB...
Robots.txt
File Detected
Sitemap.xml
File Detected
Page Size
Code & Text Ratio
Document Size: ~46.05 KB
Code Size: ~23.64 KB
Text Size: ~22.41 KB Ratio: 48.67%
Social Data
Delicious
Total: 0
Facebook
Total: 0
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
First CPU Idle
1.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/).
Serve images in next-gen formats
Potential savings of 266 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
Total Blocking Time
0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Max Potential First Input Delay
20 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Serve static assets with an efficient cache policy
30 resources found
A long cache lifetime can speed up repeat visits to your page
Eliminate render-blocking resources
Potential savings of 1,040 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
First Meaningful Paint
1.4 s
First Meaningful Paint measures when the primary content of a page is visible
Remove unused CSS
Potential savings of 44 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
Avoids enormous network payloads
Total size was 958 KiB
Large network payloads cost users real money and are highly correlated with long load times
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
Efficiently encode images
Potential savings of 12 KiB
Optimized images load faster and consume less cellular data
Speed Index
1.4 s
Speed Index shows how quickly the contents of a page are visibly populated
Avoid chaining critical requests
29 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
Avoid long main-thread tasks
1 long task found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport
Cumulative Layout Shift
0.001
Cumulative Layout Shift measures the movement of visible elements within the viewport
Avoids an excessive DOM size
331 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
0.5 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
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
Largest Contentful Paint
2.2 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Initial server response time was short
Root document took 120 ms
Keep the server response time for the main document short because all other requests depend on it
First Contentful Paint
1.1 s
First Contentful Paint marks the time at which the first 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
JavaScript execution time
0.1 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Time to Interactive
1.4 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Enable text compression
Potential savings of 3 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Links do not have descriptive text
10 links found
Descriptive link text helps search engines understand your content
Keep request counts low and transfer sizes small
46 requests • 958 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
4 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Mobile
First Meaningful Paint
4.7 s
First Meaningful Paint measures when the primary content of a page is visible
Avoids enormous network payloads
Total size was 734 KiB
Large network payloads cost users real money and are highly correlated with long load times
Largest Contentful Paint
6.9 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Links do not have descriptive text
10 links found
Descriptive link text helps search engines understand your content
Time to Interactive
5.4 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Keep request counts low and transfer sizes small
43 requests • 734 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
First Contentful Paint
3.8 s
First Contentful Paint marks the time at which the first text or image is painted
Max Potential First Input Delay
70 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
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
Avoids an excessive DOM size
331 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
5 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
Efficiently encode images
Potential savings of 12 KiB
Optimized images load faster and consume less cellular data
First Contentful Paint (3G)
7230 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
First CPU Idle
4.7 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/).
Initial server response time was short
Root document took 70 ms
Keep the server response time for the main document short because all other requests depend on it
Speed Index
3.9 s
Speed Index shows how quickly the contents of a page are visibly populated
Serve static assets with an efficient cache policy
30 resources found
A long cache lifetime can speed up repeat visits to your page
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
Total Blocking Time
70 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Eliminate render-blocking resources
Potential savings of 2,700 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport
Serve images in next-gen formats
Potential savings of 266 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
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
JavaScript execution time
0.5 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Remove unused CSS
Potential savings of 44 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
Tap targets are not sized appropriately
84% 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 chaining critical requests
29 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
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
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
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
Warning! You have broken links
View links
Alexa Rank
5,139
Local Rank: TW / Users: 17.2% / PageViews: 47.9%83,225
Global RankDomain Available
| Domain (TDL) and Typo | Status |
|---|---|
| kenzato.co | Available Buy Now! |
| kenzato.us | Available Buy Now! |
| kenzato.com | Already Registered |
| kenzato.org | Available Buy Now! |
| kenzato.net | Available Buy Now! |
| knzato.uk | Available Buy Now! |
| ienzato.uk | Available Buy Now! |
| oenzato.uk | 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: Tue, 04 Aug 2020 06:35:19 GMT
content-type: text/html; charset=UTF-8
set-cookie: __cfduid=d8046e3f97acceff83c858e690fc3b0071596522919; expires=Thu, 03-Sep-20 06:35:19 GMT; path=/; domain=.kenzato.uk; HttpOnly; SameSite=Lax; Secure
link: ; rel="https://api.w.org/"
cache-control: public, max-age=172800
expires: Wed, 05 Aug 2020 10:01:37 GMT
x-litespeed-cache: hit
x-content-type-options: nosniff
x-xss-protection: 1; mode=block
x-turbo-charged-by: LiteSpeed
cf-cache-status: DYNAMIC
cf-request-id: 0459c78fdc0000ebc5b71bf200000001
expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
server: cloudflare
cf-ray: 5bd641f96f13ebc5-LAX
content-encoding: gzip
Click to Add/Show Comments