Your Website Score is

Similar Ranking

27
BCA - SENANTIASA DI SISI ANDA
bca.co.id
27
INDONESIA INTERNET PUBLISHING, ADVERTISING AND MARKETING COMMUNITY
ads.id
27
SEOBILITY | DAS SEO TOOL FÜR ONPAGE OPTIMIERUNG
seobility.net
27
MASTERPOKER88 SITUS JUDI POKER ONLINE UANG ASLI TERPERCAYA 2020
masterhoki.com
27
INTODNS: CHECKS DNS AND MAIL SERVERS HEALTH
intodns.com
27
SOLUSI HOSTING DOMAIN DAN WEBSITE WORDPRESS - WEBHOSTMU
webhostmu.com
27
PAYOP - ONLINE PAYMENT PROCESSING WITH 300+ METHODS
payop.com

Latest Sites

24
SPÉCIALISTE DE LA TRANSFORMATION DIGITALE INNOVANTE
agencedigitale-allianced8.com
19
PLAYSTATION 5 ONLINE STORE | BEST PLAYSTATION
best-playstation.com
19
NEWSONHY TECH NEWS MOVIES BLOGGING TOOLS GUEST POST MOBILES PACKAGE
newsonhy.online
31
HOME | CURRENCY CLAN |YOUR CURRENCY BUDDY
currencyclan.com
3
MILLIONS OF SEO BACKLINKS - 1 BILLION LINKS
1billionlinks.com
58
MUSLIM.OR.ID - MEMURNIKAN AQIDAH MENEBARKAN SUNNAH
muslim.or.id
19
MOVIEXFILM | FILMS FULL HD | WATCH MOVIES ONLINE
moviexfilm.com

Top Technologies

Google Font API
Font Scripts
WordPress
CMS
CloudFlare
CDN
Nginx
Web Servers
Font Awesome
Font Scripts
Google Tag Manager
Tag Managers
Apache
Web Servers
LiteSpeed
Web Servers

27 drakor-id.cam Last Updated: 7 months

Success 55% of passed verification steps
Warning 38% of total warning
Errors 7% of total errors, require fast action

Desktop

Mobile

Performance Desktop Score 74%
Best Practices Desktop Score 79%
SEO Desktop Score 92%
Progressive Web App Desktop Score 15%
Performance Mobile Score 38%
Best Practices Mobile Score 79%
SEO Mobile Score 92%
Progressive Web App Mobile Score 18%
Page Authority Authority 24%
Domain Authority Domain Authority 11%
Moz Rank 2.4/10
Bounce Rate Rate 0%
charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 49 Characters
DRAKOR-ID | FILM DAN SERIAL TV SUBTITLE INDONESIA
Meta Description 156 Characters
Drakor-ID adalah tempat terbaik buat nonton drakor, streaming drama Korea, KorDramas dan Drakorindo. Video format terbaik serasa menonton bioskop 21 online.
Effective URL 20 Characters
http://91.230.121.37
Excerpt Page content
Drakor-ID | Film dan Serial TV Subtitle Indonesia Skip to content Close MenuIndex MovieCara DownloadMenampilkan Subtitle Setelah DownloadHomeHDBest RatingOrder by titleGenreActionAdventureComedyCrimeDramaFantasyFilm SemiMysteryRomanceScience Fict...
Keywords Cloud Density
watch68 movie55 trailer46 index39 drama32 korea23 iljimae18 film18 episode17 semi12
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
watch 68
movie 55
trailer 46
index 39
drama 32
korea 23
iljimae 18
film 18
episode 17
semi 12
Google Preview Your look like this in google search result
DRAKOR-ID | FILM DAN SERIAL TV SUBTITLE INDONESIA
http://91.230.121.37
Drakor-ID adalah tempat terbaik buat nonton drakor, streaming drama Korea, KorDramas dan Drakorindo. Video format terbaik serasa menonton bioskop 21 o
Robots.txt File Detected
Sitemap.xml File Detected
Page Size Code & Text Ratio
Document Size: ~198.7 KB
Code Size: ~182.87 KB
Text Size: ~15.83 KB Ratio: 7.97%

Social Data

Estimation Traffic and Earnings

642
Unique Visits
Daily
1,187
Pages Views
Daily
$1
Income
Daily
17,976
Unique Visits
Monthly
33,830
Pages Views
Monthly
$25
Income
Monthly
208,008
Unique Visits
Yearly
398,832
Pages Views
Yearly
$264
Income
Yearly

Technologies

PWA - Manifest

Manifest is not valid
Your site don't have valid manifest.json, read more in Web App Manifest

Desktop

Desktop Screenshot
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
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
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
Efficiently encode images Potential savings of 30 KiB
Optimized images load faster and consume less cellular data
Page load is not fast enough on mobile networks Interactive on simulated mobile network at 11.3 s
A fast page load over a cellular network ensures a good mobile user experience
Avoid an excessive DOM size 2,313 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 0.8 s
First Contentful Paint marks the time at which the first text or image is painted
Properly size images Potential savings of 439 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Keep request counts low and transfer sizes small 177 requests • 3,146 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
JavaScript execution time 0.3 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Total Blocking Time 80 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Cumulative Layout Shift 0.189
Cumulative Layout Shift measures the movement of visible elements within the viewport
Largest Contentful Paint 2.9 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Speed Index 2.0 s
Speed Index shows how quickly the contents of a page are visibly populated
Reduce initial server response time Root document took 1,210 ms
Keep the server response time for the main document short because all other requests depend on it
First CPU Idle 1.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/).
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
Minify CSS Potential savings of 3 KiB
Minifying CSS files can reduce network payload sizes
First Meaningful Paint 0.8 s
First Meaningful Paint measures when the primary content of a page is visible
Avoid enormous network payloads Total size was 3,146 KiB
Large network payloads cost users real money and are highly correlated with long load times
Remove unused CSS Potential savings of 51 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
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
Avoid chaining critical requests 14 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 serving legacy JavaScript to modern browsers Potential savings of 9 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 large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
Remove unused JavaScript Potential savings of 21 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Enable text compression Potential savings of 26 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Max Potential First Input Delay 150 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Use video formats for animated content Potential savings of 1,228 KiB
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes
Serve images in next-gen formats Potential savings of 38 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
Minimize third-party usage Third-party code blocked the main thread for 50 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
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
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
Minimizes main-thread work 1.3 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Does not use HTTPS 69 insecure requests found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding [mixed content](https://developers.google.com/web/fundamentals/security/prevent-mixed-content/what-is-mixed-content), where some resources are loaded over HTTP despite the initial request being servedover HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs
Eliminate render-blocking resources Potential savings of 470 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Serve static assets with an efficient cache policy 16 resources found
A long cache lifetime can speed up repeat visits to your page
Time to Interactive 2.5 s
Time to interactive is the amount of time it takes for the page to become fully interactive

Mobile

Mobile Screenshot
Minimize main-thread work 4.7 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
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
First Meaningful Paint 3.1 s
First Meaningful Paint measures when the primary content of a page is visible
Remove unused CSS Potential savings of 52 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
Does not use HTTPS 29 insecure requests found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding [mixed content](https://developers.google.com/web/fundamentals/security/prevent-mixed-content/what-is-mixed-content), where some resources are loaded over HTTP despite the initial request being servedover HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs
Largest Contentful Paint 20.4 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Estimated Input Latency 140 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 enormous network payloads Total size was 2,850 KiB
Large network payloads cost users real money and are highly correlated with long load times
Remove unused JavaScript Potential savings of 21 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Reduce initial server response time Root document took 1,250 ms
Keep the server response time for the main document short because all other requests depend on it
Avoid long main-thread tasks 8 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
First Contentful Paint 2.6 s
First Contentful Paint marks the time at which the first text or image is painted
Avoid chaining critical requests 14 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
Minify CSS Potential savings of 3 KiB
Minifying CSS files can reduce network payload sizes
First CPU Idle 5.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/).
Keep request counts low and transfer sizes small 94 requests • 2,850 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Document uses legible font sizes 99.42% 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
Total Blocking Time 640 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
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
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Enable text compression Potential savings of 25 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Time to Interactive 10.2 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Page load is not fast enough on mobile networks Interactive at 10.2 s
A fast page load over a cellular network ensures a good mobile user experience
Tap targets are not sized appropriately 96% 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
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
Serve static assets with an efficient cache policy 13 resources found
A long cache lifetime can speed up repeat visits to your page
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
Minimize third-party usage Third-party code blocked the main thread for 50 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 Contentful Paint (3G) 5339 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Avoid serving legacy JavaScript to modern browsers Potential savings of 9 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
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 Index 6.7 s
Speed Index shows how quickly the contents of a page are visibly populated
Max Potential First Input Delay 630 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Cumulative Layout Shift 0.022
Cumulative Layout Shift measures the movement of visible elements within the viewport
Eliminate render-blocking resources Potential savings of 1,590 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Avoid an excessive DOM size 2,313 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)
Use video formats for animated content Potential savings of 1,228 KiB
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes

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
Warning! Your website is not SSL secured (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

Alexa Rank

265,630

Global Rank

265,630

Global
Traffic
Search

Information Server

Response Header HTTP headers carry information about the client browser, the requested page and the server
HTTP/1.1 200 OK
Server: nginx
Date: Fri, 27 Nov 2020 15:42:31 GMT
Content-Type: text/html; charset=UTF-8
Connection: close
Vary: Accept-Encoding
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block
X-Frame-Options: SAMEORIGIN
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
Content-Encoding: gzip
DNS Records DNS Resource Records associated with a hostname
View DNS Records

Comments