Your Website Score is
SEO Rank : 16 Website URL: m4ufree.online Last Updated: 6 months
Success
47% of passed verification steps
Warning
38% of total warning
Errors
15% of total errors, require fast action
Share
Estimation Traffic and Earnings
46
Unique Visits
Daily
85
Pages Views
Daily
$0
Income
Daily
1,288
Unique Visits
Monthly
2,423
Pages Views
Monthly
$0
Income
Monthly
14,904
Unique Visits
Yearly
28,560
Pages Views
Yearly
$0
Income
Yearly
Desktop
Mobile
Moz Authority Rank
Page Authority
Authority 33%
Domain Authority
Domain Authority 17%
Moz Rank
3.3/10
Bounce Rate
Rate 0%
Meta Data
Charset
Encoding
Great, language/character encoding is specified: UTF-8
Title Tag
75 Characters
123MOVIES - WATCH MOVIES ONLINE FOR FREE & ALL KIND OF MOVIES AND ANIME
Meta Description
154 Characters
Putlocker - Best website to watch movies for all kind of movies for free and tv series and also anime and asian dramas, All in one just one click to play.
Effective URL
24 Characters
http://123movies123.live
Excerpt
Page content
123Movies - Watch Movies Online For Free & All Kind Of Movies and Anime
Search Now!
Home
...
Meta Keywords
5 Detected
Google Preview
Your look like this in google search result
123MOVIES - WATCH MOVIES ONLINE FOR FREE & ALL KIND OF M
http://123movies123.live
Putlocker - Best website to watch movies for all kind of movies for free and tv series and also anime and asian dramas, All in one just one click to p
Robots.txt
File Detected
Sitemap.xml
File Detected
Page Size
Code & Text Ratio
Document Size: ~72.71 KB
Code Size: ~66.42 KB
Text Size: ~6.29 KB Ratio: 8.65%
Social Data
Desktop
Minify JavaScript
Potential savings of 5 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
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
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
Cumulative Layout Shift
0.22
Cumulative Layout Shift measures the movement of visible elements within the viewport
robots.txt is not valid
195 errors found
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed
Total Blocking Time
10 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Avoid large layout shifts
5 elements found
These DOM elements contribute most to the CLS of the page.
Time to Interactive
1.0 s
Time to interactive is the amount of time it takes for the page to become fully interactive
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
Remove unused CSS
Potential savings of 69 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
Serve static assets with an efficient cache policy
16 resources found
A long cache lifetime can speed up repeat visits to your page
Minimizes main-thread work
0.6 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
49 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
First Contentful Paint
0.7 s
First Contentful Paint marks the time at which the first text or image is painted
Serve images in next-gen formats
Potential savings of 68 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
Eliminate render-blocking resources
Potential savings of 720 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Avoid chaining critical requests
11 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
Max Potential First Input Delay
60 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Largest Contentful Paint
1.3 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Remove unused JavaScript
Potential savings of 98 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Reduce initial server response time
Root document took 870 ms
Keep the server response time for the main document short because all other requests depend on it
First Meaningful Paint
0.7 s
First Meaningful Paint measures when the primary content of a page is visible
Speed Index
1.7 s
Speed Index shows how quickly the contents of a page are visibly populated
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
Avoids enormous network payloads
Total size was 1,490 KiB
Large network payloads cost users real money and are highly correlated with long load times
Avoids an excessive DOM size
531 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 CPU Idle
0.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/).
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
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
Keep request counts low and transfer sizes small
62 requests • 1,490 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport
Properly size images
Potential savings of 853 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Includes front-end JavaScript libraries with known security vulnerabilities
6 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Mobile
Total Blocking Time
190 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Cumulative Layout Shift
0.175
Cumulative Layout Shift measures the movement of visible elements within the viewport
Remove unused JavaScript
Potential savings of 98 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Does not use HTTPS
49 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
Time to Interactive
7.5 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Reduce initial server response time
Root document took 860 ms
Keep the server response time for the main document short because all other requests depend on it
Avoids enormous network payloads
Total size was 1,490 KiB
Large network payloads cost users real money and are highly correlated with long load times
First Contentful Paint (3G)
5026 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Eliminate render-blocking resources
Potential savings of 2,130 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
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
Remove unused CSS
Potential savings of 69 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
Avoid large layout shifts
5 elements found
These DOM elements contribute most to the CLS of the page.
Estimated Input Latency
40 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
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
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
First Meaningful Paint
2.5 s
First Meaningful Paint measures when the primary content of a page is visible
First Contentful Paint
2.5 s
First Contentful Paint marks the time at which the first text or image is painted
Serve static assets with an efficient cache policy
16 resources found
A long cache lifetime can speed up repeat visits to your page
Largest Contentful Paint
4.7 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Serve images in next-gen formats
Potential savings of 68 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
5 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Keep request counts low and transfer sizes small
62 requests • 1,490 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
6 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 284 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Avoids an excessive DOM size
531 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)
Speed Index
4.4 s
Speed Index shows how quickly the contents of a page are visibly populated
Minify JavaScript
Potential savings of 5 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
robots.txt is not valid
195 errors found
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed
Max Potential First Input Delay
260 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
JavaScript execution time
0.9 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Avoid chaining critical requests
11 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 CPU Idle
3.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/).
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
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
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
| First 0 Links | Relationship | HTTP Status |
Alexa Rank
0
Local Rank: / Users: / PageViews:9,698,266
Global RankDomain Available
| Domain (TDL) and Typo | Status |
|---|---|
| m4ufree.co | Already Registered |
| m4ufree.us | Already Registered |
| m4ufree.com | Already Registered |
| m4ufree.org | Already Registered |
| m4ufree.net | Already Registered |
| mufree.online | Already Registered |
| j4ufree.online | Available Buy Now! |
| i4ufree.online | 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, 06 Aug 2020 13:37:04 GMT
Content-Type: text/html;charset=UTF-8
Connection: keep-alive
Set-Cookie: __cfduid=d9716bc1b9403f2f98cdff493e4f533c31596721022; expires=Sat, 05-Sep-20 13:37:02 GMT; path=/; domain=.123movies123.live; HttpOnly; SameSite=Lax
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
CF-Cache-Status: DYNAMIC
cf-request-id: 0465965ee20000988d88bfc200000001
Server: cloudflare
CF-RAY: 5be92677dcf0988d-LAX
Content-Encoding: gzip
Click to Add/Show Comments