Your Website Score is
SEO Rank : 1 Website URL: duboku.net Last Updated: 2 months
Success
47% of passed verification steps
Warning
23% of total warning
Errors
30% 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 33%
Domain Authority
Domain Authority 21%
Moz Rank
3.3/10
Bounce Rate
Rate 0%
Meta Data
Charset
Encoding
Great, language/character encoding is specified: UTF-8
Title Tag
3 Characters
独播库
Meta Description
74 Characters
独播库,线上看,免费在线观看,电影,电视剧,动漫,视频网站,高清视频,Series,Movie,TV Shows,Online Free Watch
Effective URL
21 Characters
https://www.duboku.tv
Excerpt
Page content
独播库
首页
连续剧
电影
...
Meta Keywords
12 Detected
Google Preview
Your look like this in google search result
独播库
https://www.duboku.tv
独播库,线上看,免费在线观看,电影,电视剧,动漫,视频网站,高清视频,Series,Movie,TV Shows,Online Free Watch
Robots.txt
File Detected
Sitemap.xml
File No Found
Whois
Is a query and response protocol that is widely used for querying databases that store the registered users or assignees of an Internet resource, such as a domain name, an IP address block, or an autonomous system
Updated: 2018-10-09 / 3 years
Create on: 2018-09-17 / 3 years
Expires on: 2020-09-17 / 7 months 7 days
GoDaddy.com, LLC ,
Registrar Whois Server: whois.godaddy.com
Registrar URL: http://www.godaddy.com
Nameservers
CHAD.NS.CLOUDFLARE.COM
MICHELLE.NS.CLOUDFLARE.COM
Page Size
Code & Text Ratio
Document Size: ~82.48 KB
Code Size: ~60.26 KB
Text Size: ~22.22 KB Ratio: 26.94%
Social Data
Delicious
Total: 0
Facebook
Total: 1,318
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
Preload key requests
Potential savings of 240 ms
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load
Time to Interactive
0.9 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Remove unused JavaScript
Potential savings of 51 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
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 images in next-gen formats
Potential savings of 535 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
20 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
987 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)
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 Index
0.9 s
Speed Index shows how quickly the contents of a page are visibly populated
Max Potential First Input Delay
90 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
Minimize third-party usage
Third-party code blocked the main thread for 0 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
Keep request counts low and transfer sizes small
43 requests • 1,178 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Avoid long main-thread tasks
2 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Minimizes main-thread work
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
Avoids enormous network payloads
Total size was 1,178 KiB
Large network payloads cost users real money and are highly correlated with long load times
Largest Contentful Paint
0.8 s
Largest Contentful Paint marks the time at which the largest text or image is painted
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
Efficiently encode images
Potential savings of 223 KiB
Optimized images load faster and consume less cellular data
Minify JavaScript
Potential savings of 7 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Includes front-end JavaScript libraries with known security vulnerabilities
8 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Serve static assets with an efficient cache policy
31 resources found
A long cache lifetime can speed up repeat visits to your page
Initial server response time was short
Root document took 270 ms
Keep the server response time for the main document short because all other requests depend on it
Avoid large layout shifts
2 elements found
These DOM elements contribute most to the CLS of the page.
JavaScript execution time
0.2 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
First Contentful Paint
0.4 s
First Contentful Paint marks the time at which the first text or image is painted
First CPU Idle
0.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/).
Avoid serving legacy JavaScript to modern browsers
Potential savings of 0 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
Avoid chaining critical requests
16 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
First Meaningful Paint
0.5 s
First Meaningful Paint measures when the primary content of a page is visible
Mobile
Remove unused JavaScript
Potential savings of 51 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport
First Contentful Paint (3G)
7186 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Serve static assets with an efficient cache policy
16 resources found
A long cache lifetime can speed up repeat visits to your page
Keep request counts low and transfer sizes small
37 requests • 794 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Initial server response time was short
Root document took 400 ms
Keep the server response time for the main document short because all other requests depend on it
First CPU Idle
4.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/).
First Meaningful Paint
3.9 s
First Meaningful Paint measures when the primary content of a page is visible
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
Max Potential First Input Delay
280 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
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
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
Minimize main-thread work
5.0 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 270 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 long main-thread tasks
10 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
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
Includes front-end JavaScript libraries with known security vulnerabilities
8 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Cumulative Layout Shift
0.007
Cumulative Layout Shift measures the movement of visible elements within the viewport
Largest Contentful Paint
6.4 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Minimize third-party usage
Third-party code blocked the main thread for 80 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
Avoids enormous network payloads
Total size was 794 KiB
Large network payloads cost users real money and are highly correlated with long load times
Speed Index
5.4 s
Speed Index shows how quickly the contents of a page are visibly populated
Reduce JavaScript execution time
1.4 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Defer offscreen images
Potential savings of 84 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Efficiently encode images
Potential savings of 140 KiB
Optimized images load faster and consume less cellular data
Time to Interactive
6.3 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Estimated Input Latency
60 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
Avoid an excessive DOM size
1,001 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 serving legacy JavaScript to modern browsers
Potential savings of 0 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
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
1 element found
These DOM elements contribute most to the CLS of the page.
First Contentful Paint
3.7 s
First Contentful Paint marks the time at which the first text or image is painted
Avoid chaining critical requests
16 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
Eliminate render-blocking resources
Potential savings of 2,880 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Total Blocking Time
400 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Preload key requests
Potential savings of 630 ms
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load
Minify JavaScript
Potential savings of 7 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
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
Warning! Not found a sitemap file for your website
SSL Secure
Congratulations! Your site have Support to HTTPS
Headings
Warning! Your page not contain any H1 and H2 headings. H1 and H2 headings help indicate the important topics of your page to search engines
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 |
| http://duboku.net/ | Internal Link | 301 |
| 连续剧 | Internal Link | 301 |
| 电影 | Internal Link | 301 |
| 综艺 | Internal Link | 301 |
| 动漫 | Internal Link | 301 |
| 港剧 | Internal Link | 301 |
| 陆剧 | Internal Link | 301 |
| 日韩剧 | Internal Link | 301 |
| 英美剧 | Internal Link | 301 |
| 台泰剧 | Internal Link | 301 |
| 最近更新 | Internal Link | 301 |
| 有翡 | Internal Link | 301 |
| 天巡者 | Internal Link | 301 |
| 女神降临 | Internal Link | 301 |
| 爱的厘米 | Internal Link | 301 |
| 从结婚开始恋爱 | Internal Link | 301 |
| 九尾狐传 | Internal Link | 301 |
| 如意芳霏 | Internal Link | 301 |
| 半是蜜糖半是伤 | Internal Link | 301 |
| 流金岁月 | Internal Link | 301 |
Alexa Rank
0
Local Rank: / Users: / PageViews:
Global Rank
Domain Available
| Domain (TDL) and Typo | Status |
|---|---|
| duboku.co | Already Registered |
| duboku.us | Already Registered |
| duboku.com | Already Registered |
| duboku.org | Already Registered |
| duboku.net | Already Registered |
| dboku.net | Already Registered |
| euboku.net | Already Registered |
| cuboku.net | Already Registered |
Information Server
Response Header
HTTP headers carry information about the client browser, the requested page and the server
HTTP/2 200
date: Sun, 07 Mar 2021 13:12:19 GMT
content-type: text/html; charset=utf-8
set-cookie: __cfduid=d27d68e8f70ee6583f60ccc2a8bb2898f1615122738; expires=Tue, 06-Apr-21 13:12:18 GMT; path=/; domain=.duboku.tv; HttpOnly; SameSite=Lax; Secure
vary: Accept-Encoding
cf-cache-status: DYNAMIC
cf-request-id: 08ae6a47040000ebd534051000000001
expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
server: cloudflare
cf-ray: 62c4131e6982ebd5-LAX
content-encoding: gzip
Click to Add/Show Comments