Your Website Score is
SEO Rank : 12 Website URL: moviecafe.download Last Updated: 5 months
Success
39% of passed verification steps
Warning
23% of total warning
Errors
38% of total errors, require fast action
Share
Estimation Traffic and Earnings
72
Unique Visits
Daily
133
Pages Views
Daily
$0
Income
Daily
2,016
Unique Visits
Monthly
3,791
Pages Views
Monthly
$0
Income
Monthly
23,328
Unique Visits
Yearly
44,688
Pages Views
Yearly
$0
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
55 Characters
MOVIECAFE | WATCH WORLD LATEST MOVIES & TV SHOWS ONLINE
Meta Description
105 Characters
Watch World Latest Movies & TV Shows Online. Watch Your favorite Movies and TV-Series in HD quality Free.
Effective URL
25 Characters
http://moviecafe.download
Excerpt
Page content
MovieCafe | Watch World Latest Movies & TV Shows Online
...
Meta Keywords
10 Detected
Google Preview
Your look like this in google search result
MOVIECAFE | WATCH WORLD LATEST MOVIES & TV SHOWS ONLINE
http://moviecafe.download
Watch World Latest Movies & TV Shows Online. Watch Your favorite Movies and TV-Series in HD quality Free.
Robots.txt
File No Found
Sitemap.xml
File No Found
Page Size
Code & Text Ratio
Document Size: ~216.41 KB
Code Size: ~165.38 KB
Text Size: ~51.03 KB Ratio: 23.58%
Social Data
Desktop
Avoids enormous network payloads
Total size was 1,062 KiB
Large network payloads cost users real money and are highly correlated with long load times
Minimize main-thread work
3.9 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Minimize third-party usage
Third-party code blocked the main thread for 20 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
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
First Contentful Paint
1.0 s
First Contentful Paint marks the time at which the first text or image is painted
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
Serve images in next-gen formats
Potential savings of 243 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
Serve static assets with an efficient cache policy
33 resources found
A long cache lifetime can speed up repeat visits to your page
Eliminate render-blocking resources
Potential savings of 880 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
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
Avoid large layout shifts
5 elements found
These DOM elements contribute most to the CLS of the page.
Page load is not fast enough on mobile networks
Interactive on simulated mobile network at 11.1 s
A fast page load over a cellular network ensures a good mobile user experience
Avoid an excessive DOM size
2,785 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)
Largest Contentful Paint
2.2 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Defer offscreen images
Potential savings of 91 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Minify CSS
Potential savings of 2 KiB
Minifying CSS files can reduce network payload sizes
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport
Includes front-end JavaScript libraries with known security vulnerabilities
7 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Efficiently encode images
Potential savings of 155 KiB
Optimized images load faster and consume less cellular data
Keep request counts low and transfer sizes small
157 requests • 1,062 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Cumulative Layout Shift
0.049
Cumulative Layout Shift measures the movement of visible elements within the viewport
Does not use HTTPS
47 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
Remove unused JavaScript
Potential savings of 20 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Total Blocking Time
20 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Remove unused CSS
Potential savings of 20 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
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
Enable text compression
Potential savings of 6 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Avoid long main-thread tasks
7 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
First Meaningful Paint
1.3 s
First Meaningful Paint measures when the primary content of a page is visible
Time to Interactive
2.8 s
Time to interactive is the amount of time it takes for the page to become fully interactive
First CPU Idle
1.3 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/).
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
Minify JavaScript
Potential savings of 12 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Speed Index
2.6 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
Reduce initial server response time
Root document took 1,940 ms
Keep the server response time for the main document short because all other requests depend on it
Mobile
Cumulative Layout Shift
0.002
Cumulative Layout Shift measures the movement of visible elements within the viewport
Avoid long main-thread tasks
9 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Serve images in next-gen formats
Potential savings of 450 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
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/).
Time to Interactive
9.0 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport
Total Blocking Time
230 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Avoid chaining critical requests
27 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
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 20 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Keep request counts low and transfer sizes small
108 requests • 1,122 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Minify CSS
Potential savings of 2 KiB
Minifying CSS files can reduce network payload sizes
Remove unused CSS
Potential savings of 30 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
Reduce initial server response time
Root document took 2,080 ms
Keep the server response time for the main document short because all other requests depend on it
Minimize main-thread work
6.7 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Minify JavaScript
Potential savings of 12 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
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
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
2,798 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)
Eliminate render-blocking resources
Potential savings of 2,550 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Tap targets are not sized appropriately
85% 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
Includes front-end JavaScript libraries with known security vulnerabilities
7 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Does not use HTTPS
53 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
Avoids enormous network payloads
Total size was 1,122 KiB
Large network payloads cost users real money and are highly correlated with long load times
Largest Contentful Paint
5.8 s
Largest Contentful Paint marks the time at which the largest text or image is painted
First Meaningful Paint
3.4 s
First Meaningful Paint measures when the primary content of a page is visible
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
Defer offscreen images
Potential savings of 54 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
First Contentful Paint
3.3 s
First Contentful Paint marks the time at which the first text or image is painted
JavaScript execution time
1.1 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Efficiently encode images
Potential savings of 295 KiB
Optimized images load faster and consume less cellular data
First Contentful Paint (3G)
6192 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
25 resources found
A long cache lifetime can speed up repeat visits to your page
Avoid large layout shifts
2 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 90 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
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
Enable text compression
Potential savings of 4 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Speed Index
7.1 s
Speed Index shows how quickly the contents of a page are visibly populated
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
Congratulations! Your description is optimized
Robots.txt
Warning! Your site not have a robots.txt file
Sitemap.xml
Warning! Not 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
Warning! You have broken links
View links
| First 20 Links | Relationship | HTTP Status |
| http://moviecafe.download/ | Internal Link | 200 |
| Register | Internal Link | 404 |
| MOVIES | Internal Link | 200 |
| SERIES | Internal Link | 200 |
| Action | Internal Link | 200 |
| Adventure | Internal Link | 200 |
| Animation | Internal Link | 200 |
| Biography | Internal Link | 200 |
| Comedy | Internal Link | 200 |
| Crime | Internal Link | 200 |
| Documentary | Internal Link | 200 |
| Drama | Internal Link | 200 |
| Family | Internal Link | 200 |
| Fantasy | Internal Link | 200 |
| Horror | Internal Link | 200 |
| Mystery | Internal Link | 200 |
| Musical | Internal Link | 200 |
| Romance | Internal Link | 200 |
| Thriller | Internal Link | 200 |
| Psychological | Internal Link | 200 |
Alexa Rank
0
Local Rank: / Users: / PageViews:5,268,754
Global RankDomain Available
| Domain (TDL) and Typo | Status |
|---|---|
| moviecafe.co | Available Buy Now! |
| moviecafe.us | Already Registered |
| moviecafe.com | Already Registered |
| moviecafe.org | Available Buy Now! |
| moviecafe.net | Already Registered |
| mviecafe.download | Available Buy Now! |
| joviecafe.download | Available Buy Now! |
| ioviecafe.download | Available Buy Now! |
Information Server
Response Header
HTTP headers carry information about the client browser, the requested page and the server
HTTP/1.1 200 OK
Date: Thu, 13 Aug 2020 16:41:32 GMT
Server: Apache
X-Powered-By: PHP/7.2.32
Cache-Control: public, max-age=3600
Set-Cookie: advanced-frontend=d74459e8c65bb3ae73909c2a7693a1aa; path=/; HttpOnly
Set-Cookie: _csrf-frontend=5199d20be68abc52059e03858064eb6934d86b6fc86842bcdd62ca73389523a4a%3A2%3A%7Bi%3A0%3Bs%3A14%3A%22_csrf-frontend%22%3Bi%3A1%3Bs%3A32%3A%22BaTAVb_nf54B9iP2c1OHn5qkGTmyDARF%22%3B%7D; path=/; HttpOnly
Last-Modified: Thu, 01 Jan 1970 00:33:40 GMT
Cache-Control: max-age=2592000
Expires: Sat, 12 Sep 2020 16:41:32 GMT
Vary: User-Agent
Content-Type: text/html; charset=UTF-8
Click to Add/Show Comments