Your Website Score is
SEO Rank : 19 Website URL: rmz.cr Last Updated: 9 months
Success
55% of passed verification steps
Warning
15% of total warning
Errors
30% of total errors, require fast action
Share
Estimation Traffic and Earnings
4,519
Unique Visits
Daily
8,360
Pages Views
Daily
$16
Income
Daily
126,532
Unique Visits
Monthly
238,260
Pages Views
Monthly
$400
Income
Monthly
1,464,156
Unique Visits
Yearly
2,808,960
Pages Views
Yearly
$4,224
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
Title Tag
12 Characters
RAPIDMOVIEZ
Meta Description
193 Characters
Download Movies and TV Shows from RapidRAR, NitroFlare, Uploaded.net, ClicknUpload, RapidRAR (Compressed), Nitroflare (Compressed), Uploaded.net (Compressed), Latest Movies and TV Shows, Page 1
Effective URL
14 Characters
https://rmz.cr
Excerpt
Page content
RapidMoviez
Sign Up
|
Sign In
...
Google Preview
Your look like this in google search result
RAPIDMOVIEZ
https://rmz.cr
Download Movies and TV Shows from RapidRAR, NitroFlare, Uploaded.net, ClicknUpload, RapidRAR (Compressed), Nitroflare (Compressed), Uploaded.net (Comp
Robots.txt
File Detected
Sitemap.xml
File No Found
Page Size
Code & Text Ratio
Document Size: ~253.15 KB
Code Size: ~210.89 KB
Text Size: ~42.26 KB Ratio: 16.69%
Social Data
Desktop
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
Properly size images
Potential savings of 658 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Remove unused JavaScript
Potential savings of 81 KiB
Remove unused JavaScript to reduce 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
Cumulative Layout Shift
0.01
Cumulative Layout Shift measures the movement of visible elements within the viewport
Speed Index
1.6 s
Speed Index shows how quickly the contents of a page are visibly populated
Largest Contentful Paint
1.2 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Avoid an excessive DOM size
3,578 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)
Avoids enormous network payloads
Total size was 1,381 KiB
Large network payloads cost users real money and are highly correlated with long load times
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/).
Minimizes main-thread work
1.1 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Eliminate render-blocking resources
Potential savings of 440 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Avoid large layout shifts
5 elements found
These DOM elements contribute most to the CLS of the page.
First Contentful Paint
0.9 s
First Contentful Paint marks the time at which the first text or image is painted
Max Potential First Input Delay
80 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Reduce initial server response time
Root document took 1,030 ms
Keep the server response time for the main document short because all other requests depend on it
Preload key requests
Potential savings of 440 ms
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load
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
Time to Interactive
1.1 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Avoid chaining critical requests
12 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 JavaScript
Potential savings of 2 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Avoid long main-thread tasks
4 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
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
Efficiently encode images
Potential savings of 70 KiB
Optimized images load faster and consume less cellular data
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 images in next-gen formats
Potential savings of 195 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
Keep request counts low and transfer sizes small
147 requests • 1,381 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
First Meaningful Paint
0.9 s
First Meaningful Paint measures when the primary content of a page is visible
Uses efficient cache policy on static assets
11 resources found
A long cache lifetime can speed up repeat visits to your page
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport
Does not use HTTPS
1 insecure request 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 CSS
Potential savings of 68 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
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
Total Blocking Time
30 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Mobile
Uses efficient cache policy on static assets
11 resources found
A long cache lifetime can speed up repeat visits to your page
Avoid chaining critical requests
12 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
7 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Minimize third-party usage
Third-party code blocked the main thread for 40 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 1,380 KiB
Large network payloads cost users real money and are highly correlated with long load times
Minify JavaScript
Potential savings of 2 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
Efficiently encode images
Potential savings of 70 KiB
Optimized images load faster and consume less cellular data
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
Preload key requests
Potential savings of 2,400 ms
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load
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
First Contentful Paint (3G)
6085 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Remove unused CSS
Potential savings of 68 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 960 ms
Keep the server response time for the main document short because all other requests depend on it
Does not use HTTPS
1 insecure request 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 element
1 element found
This is the largest contentful element painted within the viewport
Eliminate render-blocking resources
Potential savings of 950 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
Serve images in next-gen formats
Potential savings of 195 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.9 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/).
Cumulative Layout Shift
0.015
Cumulative Layout Shift measures the movement of visible elements within the viewport
Speed Index
4.0 s
Speed Index shows how quickly the contents of a page are visibly populated
Avoid large layout shifts
5 elements found
These DOM elements contribute most to the CLS of the page.
JavaScript execution time
0.7 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Max Potential First Input Delay
170 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Total Blocking Time
200 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Time to Interactive
5.1 s
Time to interactive is the amount of time it takes for the page to become fully interactive
First Meaningful Paint
3.0 s
First Meaningful Paint measures when the primary content of a page is visible
Avoid an excessive DOM size
3,578 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)
Minimize main-thread work
2.9 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
First Contentful Paint
3.0 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
Keep request counts low and transfer sizes small
147 requests • 1,380 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Largest Contentful Paint
7.6 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Remove unused JavaScript
Potential savings of 81 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
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
Warning! Not 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 |
| Sign Up | Internal Link | 301 |
| Sign In | Internal Link | 301 |
| http://rmz.cr/account/connect_facebook | Internal Link | 301 |
| http://rmz.cr/ | Internal Link | 301 |
| Popular | Internal Link | 301 |
| Watch Online | Internal Link | 301 |
| Donate | Internal Link | 301 |
| DMCA | Internal Link | 301 |
| Movies Only | Internal Link | 301 |
| TV Shows Only | Internal Link | 301 |
| General Discussion | Internal Link | 301 |
| Rapidmoviez Browser (Unblock ISP filter) | Internal Link | 301 |
| A Time to Kill S01E08 The Missing Hotelier 480p WEBRip x264-RMTeam | Internal Link | 301 |
| mkv | Internal Link | 301 |
| RMTeam [480p] | Internal Link | 301 |
| A Time to Kill | Internal Link | 301 |
| 2020 | Internal Link | 301 |
| USA | Internal Link | 301 |
| Investigation Discovery | Internal Link | 301 |
| documentary | Internal Link | 301 |
Alexa Rank
57
Local Rank: IE / Users: 42.2% / PageViews: 42.9%18,469
Global RankDomain Available
| Domain (TDL) and Typo | Status |
|---|---|
| rmz.co | Already Registered |
| rmz.us | Already Registered |
| rmz.com | Already Registered |
| rmz.org | Already Registered |
| rmz.net | Available Buy Now! |
| rz.cr | Available Buy Now! |
| cmz.cr | Available Buy Now! |
| fmz.cr | 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: Fri, 07 Aug 2020 03:21:10 GMT
content-type: text/html; charset=UTF-8
set-cookie: __cfduid=d69d35d9847a971b574cae4e861d49ded1596770469; expires=Sun, 06-Sep-20 03:21:09 GMT; path=/; domain=.rmz.cr; HttpOnly; SameSite=Lax; Secure
x-powered-by: PHP/5.3.29
cache-control: no-store, no-cache, must-revalidate
pragma: no-cache
expires: 0
vary: User-Agent,Accept-Encoding
set-cookie: rms3=a%3A5%3A%7Bs%3A10%3A%22session_id%22%3Bs%3A32%3A%229e0440eac5e3db1c5262a7aa7cba84ea%22%3Bs%3A10%3A%22ip_address%22%3Bs%3A13%3A%22162.0.229.212%22%3Bs%3A10%3A%22user_agent%22%3Bb%3A0%3Bs%3A13%3A%22last_activity%22%3Bi%3A1596770304%3Bs%3A9%3A%22user_data%22%3Bs%3A0%3A%22%22%3B%7Debae259a28c83c7499dc9fa102fc4d0518075e8e; expires=Fri, 14-Aug-2020 03:18:24 GMT; path=/
cf-cache-status: DYNAMIC
cf-request-id: 046888dde7000004df7e940200000001
expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
server: cloudflare
cf-ray: 5beddda97dab04df-LAX
content-encoding: gzip
Click to Add/Show Comments