Your Website Score is
SEO Rank : 23 Website URL: filmfree4u.ws Last Updated: 7 months
Success
32% of passed verification steps
Warning
38% 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 18%
Domain Authority
Domain Authority 4%
Moz Rank
1.8/10
Bounce Rate
Rate 0%
Meta Data
Charset
Encoding
Great, language/character encoding is specified: UTF-8
Title Tag
24 Characters
WELCOME TO FILMFREE4U.WS
Meta Description
24 Characters
Welcome to filmfree4u.ws
Effective URL
24 Characters
http://www.filmfree4u.ws
Excerpt
Page content
Welcome to filmfree4u.ws
filmfree4u.ws
Home
View Videos
View Tweets
Submit Offer
...
Google Preview
Your look like this in google search result
WELCOME TO FILMFREE4U.WS
http://www.filmfree4u.ws
Welcome to filmfree4u.ws
Robots.txt
File No Found
Sitemap.xml
File No Found
Page Size
Code & Text Ratio
Document Size: ~4.55 KB
Code Size: ~1.87 KB
Text Size: ~2.68 KB Ratio: 58.97%
Social Data
Technologies
PWA - Manifest
Manifest is not valid
Your site don't have valid manifest.json, read more in Web App Manifest
Desktop
Keep request counts low and transfer sizes small
7 requests • 50 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Avoids an excessive DOM size
62 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 chaining critical requests
4 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
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
0.5 s
Largest Contentful Paint marks the time at which the largest text or image is painted
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
Initial server response time was short
Root document took 290 ms
Keep the server response time for the main document short because all other requests depend on it
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
Uses efficient cache policy on static assets
6 resources found
A long cache lifetime can speed up repeat visits to your page
Eliminate render-blocking resources
Potential savings of 290 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
First Contentful Paint
0.5 s
First Contentful Paint marks the time at which the first text or image is painted
First CPU Idle
0.5 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
20 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Speed Index
0.5 s
Speed Index shows how quickly the contents of a page are visibly populated
Total Blocking Time
0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Minimizes main-thread work
0.1 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Time to Interactive
0.5 s
Time to interactive is the amount of time it takes for the page to become fully interactive
First Meaningful Paint
0.5 s
First Meaningful Paint measures when the primary content of a page is visible
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport
Avoids enormous network payloads
Total size was 50 KiB
Large network payloads cost users real money and are highly correlated with long load times
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
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
Mobile
First CPU Idle
1.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/).
First Contentful Paint (3G)
3440 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
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
Largest Contentful Paint
2.0 s
Largest Contentful Paint marks the time at which the largest text or image is painted
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
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
Eliminate render-blocking resources
Potential savings of 1,140 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Speed Index
1.8 s
Speed Index shows how quickly the contents of a page are visibly populated
Max Potential First Input Delay
20 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Time to Interactive
1.8 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Avoids an excessive DOM size
62 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)
Minimizes main-thread work
0.3 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Initial server response time was short
Root document took 180 ms
Keep the server response time for the main document short because all other requests depend on it
First Meaningful Paint
1.8 s
First Meaningful Paint measures when the primary content of a page is visible
Total Blocking Time
0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
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
Keep request counts low and transfer sizes small
7 requests • 50 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Uses efficient cache policy on static assets
6 resources found
A long cache lifetime can speed up repeat visits to your page
Avoids enormous network payloads
Total size was 50 KiB
Large network payloads cost users real money and are highly correlated with long load times
First Contentful Paint
1.8 s
First Contentful Paint marks the time at which the first text or image is painted
Avoid chaining critical requests
4 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
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
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
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
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
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
Warning! Your site not have a favicon
Broken Links
Congratulations! You not have broken links
View links
| First 5 Links | Relationship | HTTP Status |
| Home | Internal Link | 200 |
| View Videos | Internal Link | 200 |
| View Tweets | Internal Link | 200 |
| Submit Offer | Internal Link | 200 |
| Privacy Policy | Internal Link | 200 |
Alexa Rank
0
Local Rank: / Users: / PageViews:
Global Rank
Domain Available
| Domain (TDL) and Typo | Status |
|---|---|
| filmfree4u.co | Already Registered |
| filmfree4u.us | Available Buy Now! |
| filmfree4u.com | Already Registered |
| filmfree4u.org | Available Buy Now! |
| filmfree4u.net | Already Registered |
| flmfree4u.ws | Already Registered |
| rilmfree4u.ws | Already Registered |
| vilmfree4u.ws | Already Registered |
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: Thu, 06 Aug 2020 09:43:08 GMT
Content-Type: text/html
Connection: keep-alive
Vary: Accept-Encoding
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
Content-Encoding: gzip
X-Proxy-Cache: HIT
Click to Add/Show Comments