filmyzilla.pink

filmyzilla.pink is SSL secured

Free website and domain report on filmyzilla.pink

Last Updated: 26th April, 2020 Update Now
Overview

Snoop Summary for filmyzilla.pink

This is a free and comprehensive report about filmyzilla.pink. The domain filmyzilla.pink is currently hosted on a server located in United States with the IP address 104.18.58.250, where USD is the local currency and the local language is English. Our records indicate that filmyzilla.pink is privately registered by WhoisGuard, Inc.. Filmyzilla.pink has the potential to be earning an estimated $15 USD per day from advertising revenue. If filmyzilla.pink was to be sold it would possibly be worth $10,781 USD (based on the daily revenue potential of the website over a 24 month period). Filmyzilla.pink receives an estimated 5,177 unique visitors every day - a huge amount of traffic! This report was last updated 26th April, 2020.

What is filmyzilla.pink?

Filmyzilla.pink offers dubbed hindi/bollywood movies and tv series online, including full feature films with english subtitles. We advise against visiting websites like filmyzilla.pink due to their potentially illegal/unsafe content.

About filmyzilla.pink

Site Preview: filmyzilla.pink filmyzilla.pink
Title: FilmyZilla Bollywood Hollywood Hindi D믭 Movies Filmywap 2020
Description:
Keywords and Tags: batti gul meter chalu movie download filmyzilla, bengali movies, bengali tv shows, bollywood movies, bollywood tv shows, filmyzilla, filmyzilla fun, filmyzilla in, hindi movies, hindi tv shows, jayantabhai ki luv story full movie download filmyzilla, malayalam movies, malayalam tv shows, punjabi movies, punjabi tv shows, tamil movies, tamil tv shows, telugu movies, telugu tv shows
Related Terms: filmywap 2020, filmyzilla 2020, filmyzilla hollywood dubbed movies, filmyzilla hollywood movies, filmyzilla top 20, filmyzilla top 20 movies, filmyzilla.com
Fav Icon:
Age: Over 3 years old
Domain Created: 29th February, 2020
Domain Updated: 1st January, 2001
Domain Expires: 28th February, 2021
Review

Snoop Score

2/5

Valuation

$10,781 USD
Note: All valuation figures are estimates.

Popularity

High
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 108,667
Alexa Reach: 0.0005%
SEMrush Rank (US): 661,110
SEMrush Authority Score: 0
Moz Domain Authority: 0
Moz Page Authority: 0

Rank By Country

Country Alexa Rank
Bangladesh Flag Bangladesh 15,649
India Flag India 4,048
Pakistan Flag Pakistan 19,619

Organic vs Paid (Google Ads)

Organic Paid
Keywords: 710 0
Traffic: 1,523 0
Cost: $1,624 USD $0 USD
Traffic

Visitors

Daily Visitors: 5,177
Monthly Visitors: 157,572
Yearly Visitors: 1,889,605
Note: All visitors figures are estimates.

Visitors By Country

Country Visitors (Unique) Percentage
Bangladesh Flag Bangladesh Daily: 72
Monthly: 2,206
Yearly: 26,454
1.4%
India Flag India Daily: 4,851
Monthly: 147,645
Yearly: 1,770,560
93.7%
Other Daily: 88
Monthly: 2,679
Yearly: 32,123
1.7%
Pakistan Flag Pakistan Daily: 166
Monthly: 5,042
Yearly: 60,467
3.2%
Note: All visitors figures are estimates.
Revenue

Revenue

Daily Revenue: $15 USD
Monthly Revenue: $449 USD
Yearly Revenue: $5,385 USD
Note: All revenue figures are estimates.

Revenue By Country

Country Revenue Percentage
Bangladesh Flag Bangladesh Daily: $0 USD
Monthly: $0 USD
Yearly: $5 USD
0.1%
India Flag India Daily: $15 USD
Monthly: $447 USD
Yearly: $5,355 USD
99.4%
Other Daily: $0 USD
Monthly: $0 USD
Yearly: $0 USD
<0.1%
Pakistan Flag Pakistan Daily: $0 USD
Monthly: $2 USD
Yearly: $25 USD
0.5%
Note: All revenue figures are estimates.
SEO

Backlinks Analysis (SEMrush)

Backlinks: 39,063
Referring Domains: 9
Referring IPs: 17
Filmyzilla.pink has 39,063 backlinks according to SEMrush. 100% of these backlinks are "dofollow" (follow) links which allow the flow of link equity to pass through, which may improve filmyzilla.pink's search engine rankings. Other links are treated as 'hints' by search engines and may also pass link equity, depending on what search engines decide in each case.
100% of filmyzilla.pink's backlinks are text and image links, which are ideal for SEO. Other backlink types may be unrecognized or ignored by search engines.

Top New Follow Links

1
Source: https://filmyzilla.loan/category/208/South-indian-hindi-dubbed-movies-2017/s/1.html
Target: https://filmyzilla.pink/category/208/South-indian-hindi-dubbed-movies-2017/s/1.html

2
Source: https://filmyzilla.loan/category/217/Latest-bollywood-movies-2018/w/1.html
Target: https://filmyzilla.pink/category/217/Latest-bollywood-movies-2018/w/1.html

3
Source: https://filmyzilla.loan/movie/413/Kaththi-(2014)-south-indian-hindi-dubbed-movie.html
Target: https://filmyzilla.pink/movie/413/Kaththi-(2014)-south-indian-hindi-dubbed-movie.html

4
Source: https://filmyzilla.loan/category/279/Xxx-trilogy-(2002-to-2017)-hindi-dubbed-english-movie-series/b/1.html
Target: https://filmyzilla.pink/category/279/Xxx-trilogy-(2002-to-2017)-hindi-dubbed-english-movie-series/b/1.html

5
Source: https://filmyzilla.loan/server/2881/Kill-mode-2019-english-full-movie-web-dl.mp4.html
Target: https://filmyzilla.pink/server/2881/Kill-mode-2019-english-full-movie-web-dl.mp4.html

Top Ranking Keywords (US)

1
Keyword: filmyzilla
Ranked Page: https://filmyzilla.pink/

2
Keyword: filmyzilla in
Ranked Page: https://filmyzilla.pink/

3
Keyword: filmyzilla fun
Ranked Page: https://filmyzilla.pink/

4
Keyword: batti gul meter chalu movie download filmyzilla
Ranked Page: https://filmyzilla.pink/movie/883/Batti-gul-meter-chalu-(2018)-hindi-movie.html

5
Keyword: jayantabhai ki luv story full movie download filmyzilla
Ranked Page: https://filmyzilla.pink/movie/218/Jayantabhai-ki-luv-story-(2013)-hindi-movie.html

Domain Analysis

Value Length
Domain: filmyzilla.pink 15
Domain Name: filmyzilla 10
Extension (TLD): pink 4
Expiry Check:

Page Speed Analysis

Average Load Time:
Load Time Comparison:

PageSpeed Insights

Avg. (All Categories) 68
Performance 99
Accessibility 19
Best Practices 85
SEO 91
Progressive Web App 46
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://filmyzilla.pink/
Updated: 26th April, 2020

2.23 seconds
First Contentful Paint (FCP)
52%
32%
16%

0.01 seconds
First Input Delay (FID)
99%
0%
1%

Simulate loading on desktop
99

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for filmyzilla.pink. This includes details about optimizing page load times which can result in a better user experience.

Metrics

First Contentful Paint — 0.6 s
The time taken for the first image or text on the page to be rendered.
First Meaningful Paint — 0.8 s
The time taken for the primary content of the page to be rendered.
Speed Index — 0.8 s
The time taken for the page contents to be visibly populated.
Time to Interactive — 0.8 s
The time taken for the page to become fully interactive.
First CPU Idle — 0.8 s
The time taken for the page's main thread to be quiet enough to handle input.
Max Potential First Input Delay — 20 ms
Users could experience a delay when interacting with the page.

Other

Estimated Input Latency — 10 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive filmyzilla.pink as laggy when the latency is higher than 0.05 seconds.
Total Blocking Time — 0 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Network Requests
Below is a list of network requests that were made during page load.
URL Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://filmyzilla.pink/
0
98.235999932513
390
0
301
https://filmyzilla.pink/
98.706000018865
570.24799985811
5180
18017
200
text/html
Document
https://filmyzilla.pink/templates/css/lite.css
584.66599998064
638.0600000266
2222
6615
200
text/css
Stylesheet
https://www.googletagmanager.com/gtag/js?id=UA-116316520-1
585.0129998289
607.17400000431
30892
81637
200
application/javascript
Script
https://filmyzilla.pink/facebook.png
585.26799990796
641.75700000487
766
287
200
image/png
Image
https://filmyzilla.pink/sms.png
612.90499987081
694.01400000788
926
447
200
image/png
Image
https://filmyzilla.pink/google+.png
650.52899997681
676.77200003527
1018
539
200
image/png
Image
https://filmyzilla.pink/twitter.png
650.72999987751
672.59999993257
965
486
200
image/png
Image
https://filmyzilla.pink/whatsapp.png
650.854999898
712.98799989745
1227
748
200
image/png
Image
https://i.imgur.com/9I73k2f.gif
650.95499996096
667.84699982964
6009
5488
200
image/gif
Image
https://i.imgur.com/CIv2nTW.gif
651.09199983999
668.75499999151
5218
4697
200
image/gif
Image
https://www.google-analytics.com/analytics.js
651.37299988419
656.53000003658
18794
45229
200
text/javascript
Script
https://www.google-analytics.com/r/collect?v=1&_v=j81&a=877574970&t=pageview&_s=1&dl=https%3A%2F%2Ffilmyzilla.pink%2F&ul=en-us&de=UTF-8&dt=FilmyZilla%20Bollywood%20Hollywood%20Hindi%20Dubbed%20Movies%20Filmywap%202020&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=IEBAAUAB~&jid=1058582478&gjid=38203666&cid=1230939988.1587931501&tid=UA-116316520-1&_gid=1611626272.1587931501&_r=1&gtm=2ou4f0&z=1774362630
729.44499994628
734.18799997307
580
35
200
image/gif
Image
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
591.995
7.338
602.811
5.045
631.937
5.99
657.995
20.292
680.382
29.883
715.551
28.927
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Opportunities

Eliminate render-blocking resources — Potential savings of 0 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Filmyzilla.pink should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Size (Bytes) Potential Savings (Ms)
https://filmyzilla.pink/templates/css/lite.css
2222
70
Properly size images
Images can slow down the page's load time. Filmyzilla.pink should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Filmyzilla.pink should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Filmyzilla.pink should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Filmyzilla.pink should consider minifying JS files.
Remove unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Filmyzilla.pink should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Server response times are low (TTFB) — Root document took 470 ms
Time to First Byte (TTFB) identifies the time at which the server sends a response.
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Filmyzilla.pink should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
(Start) http://filmyzilla.pink/
0
https://filmyzilla.pink/
190
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Filmyzilla.pink should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.

Diagnostics

Avoids enormous network payloads — Total size was 72 KB
Large network payloads can cost users money and are linked to long load times.
URL Size (Bytes)
https://www.googletagmanager.com/gtag/js?id=UA-116316520-1
30892
https://www.google-analytics.com/analytics.js
18794
https://i.imgur.com/9I73k2f.gif
6009
https://i.imgur.com/CIv2nTW.gif
5218
https://filmyzilla.pink/
5180
https://filmyzilla.pink/templates/css/lite.css
2222
https://filmyzilla.pink/whatsapp.png
1227
https://filmyzilla.pink/google+.png
1018
https://filmyzilla.pink/twitter.png
965
https://filmyzilla.pink/sms.png
926
Uses efficient cache policy on static assets — 7 resources found
Filmyzilla.pink can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Size (Bytes)
https://www.google-analytics.com/analytics.js
7200000
18794
https://filmyzilla.pink/templates/css/lite.css
14400000
2222
https://filmyzilla.pink/whatsapp.png
14400000
1227
https://filmyzilla.pink/google+.png
14400000
1018
https://filmyzilla.pink/twitter.png
14400000
965
https://filmyzilla.pink/sms.png
14400000
926
https://filmyzilla.pink/facebook.png
14400000
766
Avoids an excessive DOM size — 296 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
296
Maximum DOM Depth
7
Maximum Child Elements
55
Avoid chaining critical requests — 1 chain found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Filmyzilla.pink should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.0 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
Other
75.752
3.154
0.891
Minimizes main-thread work — 0.1 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
47.261
Style & Layout
30.679
Other
23.567
Rendering
10.602
Parse HTML & CSS
7.145
Script Parsing & Compilation
4.302
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 13 requests • 72 KB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
13
74187
Script
2
49686
Image
8
16709
Document
1
5180
Stylesheet
1
2222
Other
1
390
Media
0
0
Font
0
0
Third-party
5
61493
Minimize third-party usage — Third-party code blocked the main thread for 0 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Size (Bytes) Main-Thread Blocking Time (Ms)
30892
0
19374
0

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
19

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of filmyzilla.pink. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.

Audio and video

`<audio>` elements contain a `<track>` element with `[kind="captions"]`
Filmyzilla.pink may provide assistance to deaf or hearing-impaired users with captions on audio elements.
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Filmyzilla.pink may provide assistance to deaf or hearing-impaired users with captions on videos.
`<video>` elements contain a `<track>` element with `[kind="description"]`
Filmyzilla.pink may provide relevant information that dialogue cannot, by using audio descriptions.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>` or `<template>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Presentational `<table>` elements avoid using `<th>`, `<caption>` or the `[summary]` attribute.
It is advised to not include data elements in tables which are used for layout purposes, as it may create confusion for screen reader and other assistive technology users.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Best practices

`[id]` attributes on the page are unique
It is advised to keep all id attributes unique in order to prevent instances from being overlooked by screen readers and other assistive technologies.
The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.

Internationalization and localization

`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Contrast

Background and foreground colors do not have a sufficient contrast ratio.
Many (if not most) users find low-contrast text difficult or impossible to read.
Failing Elements

Internationalization and localization

`<html>` element does not have a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
Failing Elements

Names and labels

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
img
img
Links do not have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.

Best practices

`[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.
Failing Elements

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
Headings don't skip levels
Ensure that headings create an outline for the page and that heading levels are not skipped.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
85

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that filmyzilla.pink should incorporate. This includes practices such as protecting pages with HTTPS.

Other

Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Links to cross-origin destinations are safe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.

Other

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL
http://filmyzilla.pink/
Page lacks the HTML doctype, thus triggering quirks-mode
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
91

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for filmyzilla.pink. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of filmyzilla.pink on mobile screens.
Document uses legible font sizes
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Tap targets are sized appropriately
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Content Best Practices

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
img
img

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
46

Progressive Web App

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of filmyzilla.pink. This includes details about web app manifests.

Fast and reliable

Page load is fast enough on mobile networks
Ensure that the page loads fast enough over a cellular network, to ensure good mobile user experience.

PWA Optimized

Redirects HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of filmyzilla.pink on mobile screens.
Contains some content when JavaScript is not available
Apps should display alternative content for when JavaScript is disabled.

Fast and reliable

Current page does not respond with a 200 when offline
In order for Progressive Web Apps to be made available offline, ensure that the app is using a service worker.
`start_url` does not respond with a 200 when offline
Consider using a service worker for Progressive Web Apps to ensure greater reliability for the user, in the case of poor network conditions.

Installable

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL
http://filmyzilla.pink/
Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Web app manifest does not meet the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
View Data

PWA Optimized

Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Does not provide a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Avg. (All Categories) 66
Performance 98
Accessibility 19
Best Practices 85
SEO 82
Progressive Web App 48
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://filmyzilla.pink/
Updated: 26th April, 2020

1.51 seconds
First Contentful Paint (FCP)
64%
26%
10%

0.03 seconds
First Input Delay (FID)
98%
1%
1%

Simulate loading on mobile
98

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for filmyzilla.pink. This includes details about optimizing page load times which can result in a better user experience.

Metrics

First Contentful Paint — 1.3 s
The time taken for the first image or text on the page to be rendered.
First Meaningful Paint — 1.3 s
The time taken for the primary content of the page to be rendered.
Speed Index — 1.5 s
The time taken for the page contents to be visibly populated.
Time to Interactive — 3.2 s
The time taken for the page to become fully interactive.
First CPU Idle — 3.1 s
The time taken for the page's main thread to be quiet enough to handle input.
Max Potential First Input Delay — 110 ms
Users could experience a delay when interacting with the page.

Other

Estimated Input Latency — 10 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive filmyzilla.pink as laggy when the latency is higher than 0.05 seconds.
Total Blocking Time — 30 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Network Requests
Below is a list of network requests that were made during page load.
URL Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://filmyzilla.pink/
0
26.794000004884
394
0
301
https://filmyzilla.pink/
27.470000030007
514.05200001318
5125
18017
200
text/html
Document
https://filmyzilla.pink/templates/css/lite.css
527.45300001698
578.68899998721
2222
6615
200
text/css
Stylesheet
https://www.googletagmanager.com/gtag/js?id=UA-116316520-1
527.67699997639
740.61400000937
30892
81637
200
application/javascript
Script
https://filmyzilla.pink/facebook.png
527.9590000282
548.79800003255
766
287
200
image/png
Image
https://filmyzilla.pink/sms.png
550.95699999947
596.32599999895
926
447
200
image/png
Image
https://filmyzilla.pink/google+.png
581.22400002321
608.32300002221
1018
539
200
image/png
Image
https://filmyzilla.pink/twitter.png
581.50099997874
602.05799998948
965
486
200
image/png
Image
https://filmyzilla.pink/whatsapp.png
581.68800000567
604.12500001257
1227
748
200
image/png
Image
https://i.imgur.com/9I73k2f.gif
581.77500002785
598.1160000083
6009
5488
200
image/gif
Image
https://www.google-analytics.com/analytics.js
765.66600002116
770.34099999582
18794
45229
200
text/javascript
Script
https://www.google-analytics.com/r/collect?v=1&_v=j81&a=784520039&t=pageview&_s=1&dl=https%3A%2F%2Ffilmyzilla.pink%2F&ul=en-us&de=UTF-8&dt=FilmyZilla%20Bollywood%20Hollywood%20Hindi%20Dubbed%20Movies%20Filmywap%202020&sd=24-bit&sr=412x660&vp=412x660&je=0&_u=IEBAAUAB~&jid=1649371862&gjid=1360620091&cid=819469974.1587931510&tid=UA-116316520-1&_gid=766028573.1587931510&_r=1&gtm=2ou4f0&z=565695859
801.36600002879
804.91100001382
580
35
200
image/gif
Image
https://www.google-analytics.com/collect?v=1&_v=j81&a=784520039&t=timing&_s=2&dl=https%3A%2F%2Ffilmyzilla.pink%2F&ul=en-us&de=UTF-8&dt=FilmyZilla%20Bollywood%20Hollywood%20Hindi%20Dubbed%20Movies%20Filmywap%202020&sd=24-bit&sr=412x660&vp=412x660&je=0&plt=756&pdt=0&dns=0&rrt=29&srt=487&tcp=0&dit=585&clt=585&_gst=765&_gbt=779&_cst=583&_cbt=756&_u=IEBAAUAB~&jid=&gjid=&cid=819469974.1587931510&tid=UA-116316520-1&_gid=766028573.1587931510&z=1059694076
814.41900000209
817.08200002322
593
35
200
image/gif
Image
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
556.316
7.433
619.786
9.552
629.483
26.062
659.798
7.829
786.748
6.728
794.177
11.152
813.691
27.381
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
First Contentful Paint (3G) — 2490 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.

Opportunities

Properly size images
Images can slow down the page's load time. Filmyzilla.pink should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Filmyzilla.pink should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Filmyzilla.pink should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Filmyzilla.pink should consider minifying JS files.
Remove unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Filmyzilla.pink should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Server response times are low (TTFB) — Root document took 490 ms
Time to First Byte (TTFB) identifies the time at which the server sends a response.
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Filmyzilla.pink should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
(Start) http://filmyzilla.pink/
0
https://filmyzilla.pink/
630
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Filmyzilla.pink should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.

Diagnostics

Avoids enormous network payloads — Total size was 68 KB
Large network payloads can cost users money and are linked to long load times.
URL Size (Bytes)
https://www.googletagmanager.com/gtag/js?id=UA-116316520-1
30892
https://www.google-analytics.com/analytics.js
18794
https://i.imgur.com/9I73k2f.gif
6009
https://filmyzilla.pink/
5125
https://filmyzilla.pink/templates/css/lite.css
2222
https://filmyzilla.pink/whatsapp.png
1227
https://filmyzilla.pink/google+.png
1018
https://filmyzilla.pink/twitter.png
965
https://filmyzilla.pink/sms.png
926
https://filmyzilla.pink/facebook.png
766
Uses efficient cache policy on static assets — 7 resources found
Filmyzilla.pink can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Size (Bytes)
https://www.google-analytics.com/analytics.js
7200000
18794
https://filmyzilla.pink/templates/css/lite.css
14400000
2222
https://filmyzilla.pink/whatsapp.png
14400000
1227
https://filmyzilla.pink/google+.png
14400000
1018
https://filmyzilla.pink/twitter.png
14400000
965
https://filmyzilla.pink/sms.png
14400000
926
https://filmyzilla.pink/facebook.png
14400000
766
Avoids an excessive DOM size — 296 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
296
Maximum DOM Depth
7
Maximum Child Elements
55
Avoid chaining critical requests — 1 chain found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Filmyzilla.pink should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.2 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
Other
295.96
12.88
3.588
https://www.google-analytics.com/analytics.js
122.252
116.72
5.532
https://www.googletagmanager.com/gtag/js?id=UA-116316520-1
73.964
64.688
9.276
Minimizes main-thread work — 0.5 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
194.964
Style & Layout
107.508
Other
102.32
Rendering
47.56
Parse HTML & CSS
22.104
Script Parsing & Compilation
19.66
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 13 requests • 68 KB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
13
69511
Script
2
49686
Image
8
12084
Document
1
5125
Stylesheet
1
2222
Other
1
394
Media
0
0
Font
0
0
Third-party
5
56868
Minimize third-party usage — Third-party code blocked the main thread for 50 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Size (Bytes) Main-Thread Blocking Time (Ms)
19967
49.312
30892
0

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.

Opportunities

Eliminate render-blocking resources — Potential savings of 180 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Filmyzilla.pink should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Size (Bytes) Potential Savings (Ms)
https://filmyzilla.pink/templates/css/lite.css
2222
180
19

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of filmyzilla.pink. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.

Audio and video

`<audio>` elements contain a `<track>` element with `[kind="captions"]`
Filmyzilla.pink may provide assistance to deaf or hearing-impaired users with captions on audio elements.
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Filmyzilla.pink may provide assistance to deaf or hearing-impaired users with captions on videos.
`<video>` elements contain a `<track>` element with `[kind="description"]`
Filmyzilla.pink may provide relevant information that dialogue cannot, by using audio descriptions.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>` or `<template>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Presentational `<table>` elements avoid using `<th>`, `<caption>` or the `[summary]` attribute.
It is advised to not include data elements in tables which are used for layout purposes, as it may create confusion for screen reader and other assistive technology users.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Best practices

`[id]` attributes on the page are unique
It is advised to keep all id attributes unique in order to prevent instances from being overlooked by screen readers and other assistive technologies.
The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.

Internationalization and localization

`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Contrast

Background and foreground colors do not have a sufficient contrast ratio.
Many (if not most) users find low-contrast text difficult or impossible to read.
Failing Elements

Internationalization and localization

`<html>` element does not have a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
Failing Elements

Names and labels

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
img
img
Links do not have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.

Best practices

`[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.
Failing Elements

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
Headings don't skip levels
Ensure that headings create an outline for the page and that heading levels are not skipped.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
85

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that filmyzilla.pink should incorporate. This includes practices such as protecting pages with HTTPS.

Other

Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Links to cross-origin destinations are safe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
No browser errors logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.

Other

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL
http://filmyzilla.pink/
Page lacks the HTML doctype, thus triggering quirks-mode
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
82

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for filmyzilla.pink. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of filmyzilla.pink on mobile screens.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Mobile Friendly

Tap targets are not sized appropriately — 71% appropriately sized tap targets
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.
Tap Target Size Overlapping Target
43x13
123x13
62x13
113x13
123x13
54x13

Content Best Practices

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
img
img

Mobile Friendly

Document doesn't use legible font sizes — 21.14% legible text
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Source Selector % of Page Text Font Size
https://filmyzilla.pink/:61:4
p
37.77%
11px
https://filmyzilla.pink/templates/css/lite.css:306:1
p.home
19.53%
11px
Add'l illegible text
21.56%
< 12px
Legible text
21.14%
≥ 12px

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
48

Progressive Web App

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of filmyzilla.pink. This includes details about web app manifests.

Fast and reliable

Page load is fast enough on mobile networks
Ensure that the page loads fast enough over a cellular network, to ensure good mobile user experience.

PWA Optimized

Redirects HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of filmyzilla.pink on mobile screens.
Contains some content when JavaScript is not available
Apps should display alternative content for when JavaScript is disabled.

Fast and reliable

Current page does not respond with a 200 when offline
In order for Progressive Web Apps to be made available offline, ensure that the app is using a service worker.
`start_url` does not respond with a 200 when offline
Consider using a service worker for Progressive Web Apps to ensure greater reliability for the user, in the case of poor network conditions.

Installable

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL
http://filmyzilla.pink/
Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Web app manifest does not meet the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
View Data

PWA Optimized

Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Does not provide a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Hosting

Server Location

Server IP Address: 104.18.58.250
Continent: North America
Country: United States
United States Flag
Region:
City:
Longitude: -97.822
Latitude: 37.751
Currencies: USD
USN
USS
Languages: English

Web Hosting Provider

Name IP Address
Cloudflare, Inc.
Registration

Domain Registrant

Private Registration: Yes
Name: WhoisGuard Protected
Organization: WhoisGuard, Inc.
Country: PA
City: Panama
State: Panama
Post Code:
Email: 30c9d9cc92bb4af89cba69d76659addd.protect@whoisguard.com
Phone: +507.8365503
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
NAMECHEAP INC 104.16.100.56
Security

Visitor Safety

Mature Content: Not Likely
McAfee WebAdvisor Rating:
WOT Rating:
WOT Trustworthiness:
WOT Child Safety:
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: sni.cloudflaressl.com
Issued By: CloudFlare Inc ECC CA-2
Valid From: 29th February, 2020
Valid To: 9th October, 2020
Subject: CN = sni.cloudflaressl.com
O = Cloudflare, Inc.
L = San Francisco
S = US
Hash: 4d04c09a
Issuer: CN = CloudFlare Inc ECC CA-2
O = CloudFlare, Inc.
S = US
Version: 2
Serial Number: 18630527166308954652172998442088433889
Serial Number (Hex): 0E041BE8670D439634283672765088E1
Valid From: 29th February, 2024
Valid To: 9th October, 2024
Signature Algorithm (Short Name): ecdsa-with-SHA256
Signature Algorithm (Long Name): ecdsa-with-SHA256
Authority Key Identifier: keyid:3E:74:2D:1F:CF:45:75:04:7E:3F:C0:A2:87:3E:4C:43:83:51:13:C6
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
CRL Distribution Points:
Full Name:
URI:http://crl3.digicert.com/CloudFlareIncECCCA2.crl

Full Name:
URI:http://crl4.digicert.com/CloudFlareIncECCCA2.crl

Certificate Policies: Policy: 2.16.840.1.114412.1.1
CPS: https://www.digicert.com/CPS
Policy: 2.23.140.1.2.2

Authority Information Access: OCSP - URI:http://ocsp.digicert.com
CA Issuers - URI:http://cacerts.digicert.com/CloudFlareIncECCCA-2.crt

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : B2:1E:05:CC:8B:A2:CD:8A:20:4E:87:66:F9:2B:B9:8A:
25:20:67:6B:DA:FA:70:E7:B2:49:53:2D:EF:8B:90:5E
Timestamp : Feb 29 14:46:06.168 2020 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:E2:69:00:EA:E1:81:B5:4E:5F:03:6C:
0B:AD:43:5D:9B:AC:01:88:CA:15:13:18:86:ED:E8:9F:
C5:DC:AA:25:FF:02:21:00:FD:F0:A5:C8:38:E0:AC:61:
6F:A8:FD:AC:FE:F5:98:1B:83:1B:C7:AF:17:C6:17:44:
25:0D:7B:7E:9A:1B:FD:5E
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : F0:95:A4:59:F2:00:D1:82:40:10:2D:2F:93:88:8E:AD:
4B:FE:1D:47:E3:99:E1:D0:34:A6:B0:A8:AA:8E:B2:73
Timestamp : Feb 29 14:46:06.251 2020 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:30:D8:AA:9F:F9:13:D1:A2:4A:BF:23:4B:
52:BA:AF:0F:20:70:26:96:FE:DB:6B:0D:CD:9D:9F:B5:
0B:8E:10:81:02:21:00:C5:68:F2:37:3D:EE:6D:BA:40:
78:41:FF:47:C2:54:08:93:5B:87:81:56:B6:AB:C1:93:
9D:31:FF:32:BE:C3:B7
Key Usage: Digital Signature
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:*.filmyzilla.pink
DNS:filmyzilla.pink
DNS:sni.cloudflaressl.com
Technical

DNS Lookup

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Date: 26th April, 2020
Content-Type: text/html
Server: cloudflare
Connection: keep-alive
Set-Cookie: *
CF-Cache-Status: DYNAMIC
Expect-CT: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
CF-RAY: 58a2ea5fbea7e744-EWR
cf-request-id: 0259b0cfd10000e744a82b2200000001

Whois Lookup

Created: 29th February, 2020
Changed: 1st January, 2001
Expires: 28th February, 2021
Registrar: NAMECHEAP INC
Status: clientTransferProhibited
serverTransferProhibited
Nameservers: dawn.ns.cloudflare.com
micah.ns.cloudflare.com
Owner Name: WhoisGuard Protected
Owner Organization: WhoisGuard, Inc.
Owner Street: P.O. Box 0823-03411
Owner City: Panama
Owner State: Panama
Owner Country: PA
Owner Phone: +507.8365503
Owner Email: 30c9d9cc92bb4af89cba69d76659addd.protect@whoisguard.com
Admin Name: WhoisGuard Protected
Admin Organization: WhoisGuard, Inc.
Admin Street: P.O. Box 0823-03411
Admin City: Panama
Admin State: Panama
Admin Country: PA
Admin Phone: +507.8365503
Admin Email: 30c9d9cc92bb4af89cba69d76659addd.protect@whoisguard.com
Tech Name: WhoisGuard Protected
Tech Organization: WhoisGuard, Inc.
Tech Street: P.O. Box 0823-03411
Tech City: Panama
Tech State: Panama
Tech Country: PA
Tech Phone: +507.8365503
Tech Email: 30c9d9cc92bb4af89cba69d76659addd.protect@whoisguard.com
Full Whois: Domain name: filmyzilla.pink
Registry Domain ID: D503300001183404193-LRMS
Registrar WHOIS Server: whois.namecheap.com
Registrar URL: http://www.namecheap.com
Updated Date: 0001-01-01T00:00:00.00Z
Creation Date: 2020-02-29T13:38:07.00Z
Registrar Registration Expiration Date: 2021-02-28T13:38:07.00Z
Registrar: NAMECHEAP INC
Registrar IANA ID: 1068
Registrar Abuse Contact Email: abuse@namecheap.com
Registrar Abuse Contact Phone: +1.6613102107
Reseller: NAMECHEAP INC
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: serverTransferProhibited https://icann.org/epp#serverTransferProhibited
Registry Registrant ID:
Registrant Name: WhoisGuard Protected
Registrant Organization: WhoisGuard, Inc.
Registrant Street: P.O. Box 0823-03411
Registrant City: Panama
Registrant State/Province: Panama
Registrant Postal Code:
Registrant Country: PA
Registrant Phone: +507.8365503
Registrant Phone Ext:
Registrant Fax: +51.17057182
Registrant Fax Ext:
Registrant Email: 30c9d9cc92bb4af89cba69d76659addd.protect@whoisguard.com
Registry Admin ID:
Admin Name: WhoisGuard Protected
Admin Organization: WhoisGuard, Inc.
Admin Street: P.O. Box 0823-03411
Admin City: Panama
Admin State/Province: Panama
Admin Postal Code:
Admin Country: PA
Admin Phone: +507.8365503
Admin Phone Ext:
Admin Fax: +51.17057182
Admin Fax Ext:
Admin Email: 30c9d9cc92bb4af89cba69d76659addd.protect@whoisguard.com
Registry Tech ID:
Tech Name: WhoisGuard Protected
Tech Organization: WhoisGuard, Inc.
Tech Street: P.O. Box 0823-03411
Tech City: Panama
Tech State/Province: Panama
Tech Postal Code:
Tech Country: PA
Tech Phone: +507.8365503
Tech Phone Ext:
Tech Fax: +51.17057182
Tech Fax Ext:
Tech Email: 30c9d9cc92bb4af89cba69d76659addd.protect@whoisguard.com
Name Server: dawn.ns.cloudflare.com
Name Server: micah.ns.cloudflare.com
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2020-04-25T22:04:55.65Z <<<

For more information on Whois status codes, please visit https://icann.org/epp

Nameservers

Name IP Address
dawn.ns.cloudflare.com 108.162.192.106
micah.ns.cloudflare.com 173.245.59.206
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5
0/5
$3,869 USD 2/5
0/5
$690 USD 2/5

Sites hosted on the same IP address

Domain Valuation Snoop Score
$10 USD 1/5
$4,281 USD 2/5