filmizilla.me

filmizilla.me may not be SSL secured

Free website and domain report on filmizilla.me

Last Updated: 11th February, 2023 Update Now
Overview

Snoop Summary for filmizilla.me

This is a free and comprehensive report about filmizilla.me. The domain filmizilla.me is currently hosted on a server located in Canada with the IP address 104.247.81.52, where the local currency is CAD and English is the local language. Our records indicate that filmizilla.me is owned/operated by c/o whoisproxy.com. If filmizilla.me was to be sold it would possibly be worth $228 USD (based on the daily revenue potential of the website over a 24 month period). Filmizilla.me receives an estimated 105 unique visitors every day - a decent amount of traffic! This report was last updated 11th February, 2023.

What is filmizilla.me?

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

About filmizilla.me

Site Preview: filmizilla.me filmizilla.me
Title: filmizilla.me
Description: This domain may be for sale!
Keywords and Tags: bengali movies, bengali tv shows, bollywood movies, bollywood tv shows, hindi movies, hindi tv shows, malayalam movies, malayalam tv shows, parked domain, punjabi movies, punjabi tv shows, tamil movies, tamil tv shows, telugu movies, telugu tv shows
Related Terms:
Fav Icon:
Age: Over 4 years old
Domain Created: 28th June, 2020
Domain Updated: 12th March, 2022
Domain Expires: 28th June, 2023
Review

Snoop Score

Valuation

$228 USD
Note: All valuation figures are estimates.

Popularity

Low
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 8,127,706
Alexa Reach:
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority: 1
Moz Page Authority: 5

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors: 105
Monthly Visitors: 3,196
Yearly Visitors: 38,325
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $0 USD
Monthly Revenue: $9 USD
Yearly Revenue: $109 USD
Note: All revenue figures are estimates.

Revenue By Country

SEO

Backlinks Analysis (SEMrush)

Top New Follow Links

Top Ranking Keywords (US)

Domain Analysis

Value Length
Domain: filmizilla.me 13
Domain Name: filmizilla 10
Extension (TLD): me 2
Expiry Check:

Page Speed Analysis

Average Load Time:
Load Time Comparison:

PageSpeed Insights

Avg. (All Categories) 76
Performance 98
Accessibility 86
Best Practices 85
SEO 90
PWA 22
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on desktop
98

Performance

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

Metrics

First Contentful Paint — 0.9 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 0.9 s
The time taken for the page to become fully interactive.
Speed Index — 1.1 s
The time taken for the page contents to be visibly populated.
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).
Largest Contentful Paint — 1.0 s
The timing of the largest text or image that is painted.
Cumulative Layout Shift — 0.01
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

Max Potential First Input Delay — 20 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 0.9 s
The time taken for the primary content of the page to be rendered.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://filmizilla.me/
http/1.1
0
286.28100000788
410
0
302
text/html
http://ww25.filmizilla.me/?subid1=20220102-0151-2672-87cb-6ddb00e39949
http/1.1
286.66700003669
401.60099999048
2002
1885
200
text/html
Document
http://ww25.filmizilla.me/js/parking.2.75.3.js
http/1.1
412.20000002068
608.19400008768
19796
59052
200
application/javascript
Script
http://ww25.filmizilla.me/_fd?subid1=20220102-0151-2672-87cb-6ddb00e39949
http/1.1
619.92800002918
798.90000005253
2039
2509
200
text/html
Fetch
https://www.google.com/adsense/domains/caf.js
h2
620.78400002792
633.34200007375
52670
141240
200
text/javascript
Script
http://ww25.filmizilla.me/px.gif?ch=1&rn=9.539406172849729
http/1.1
622.17600003351
734.6939999843
421
42
200
image/gif
Image
http://ww25.filmizilla.me/px.gif?ch=2&rn=9.539406172849729
http/1.1
622.4200000288
805.46800000593
421
42
200
image/gif
Image
https://www.google.com/afs/ads?psid=6512503653&pcsa=false&channel=pid-bodis-gcontrol264%2Cpid-bodis-gcontrol97%2Cpid-bodis-gcontrol314%2Cpid-bodis-gcontrol152&client=dp-bodis30_3ph&r=m&hl=en&max_radlink_len=60&type=3&uiopt=true&swp=as-drid-2166691821371338&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300769%2C17300771%2C17300842%2C17300859%2C17300862&format=r3&nocache=1671641048686818&num=0&output=afd_ads&domain_name=ww25.filmizilla.me&v=3&bsl=8&pac=0&u_his=2&u_tz=-480&dt=1641048686819&u_w=800&u_h=600&biw=1350&bih=940&psw=1334&psh=77&frm=0&uio=-&cont=rs&inames=master-1&jsv=90062&rurl=http%3A%2F%2Fww25.filmizilla.me%2F%3Fsubid1%3D20220102-0151-2672-87cb-6ddb00e39949
h2
823.80500005092
946.51500007603
2856
5577
200
text/html
Document
https://www.google.com/adsense/domains/caf.js
h2
959.80900002178
973.48600008991
52669
141249
200
text/javascript
Script
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/search.svg?c=%231967d2
h2
1015.2970000636
1018.3840000536
1188
391
200
image/svg+xml
Image
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/call_to_action_arrow.svg?c=%23ffffff
h2
1015.5900000827
1022.1340000862
1194
444
200
image/svg+xml
Image
http://ww25.filmizilla.me/_tr
1061.2050000345
1068.7010000693
0
0
-1
Fetch
https://www.google.com/afs/gen_204?client=dp-bodis30_3ph&output=uds_ads_only&zx=o21jbl2otmy&aqid=bmrQYcLYNYuNmwTgtIKoAw&psid=6512503653&pbt=bs&adbx=475&adby=65.8125&adbh=477&adbw=400&adbah=145%2C171%2C145&adbn=master-1&eawp=partner-dp-bodis30_3ph&errv=9006289805167013517&csadii=10&csadr=218&csala=10%7C141%7C33%7C44&lle=0&llm=1000&ifv=1&usr=1
h2
2540.3439999791
2561.6760000121
332
0
204
text/html
Image
https://www.google.com/afs/gen_204?client=dp-bodis30_3ph&output=uds_ads_only&zx=yxo0ai7hnfbv&aqid=bmrQYcLYNYuNmwTgtIKoAw&psid=6512503653&pbt=bv&adbx=475&adby=65.8125&adbh=477&adbw=400&adbah=145%2C171%2C145&adbn=master-1&eawp=partner-dp-bodis30_3ph&errv=9006289805167013517&csadii=10&csadr=218&csala=10%7C141%7C33%7C44&lle=0&llm=1000&ifv=1&usr=1
h2
3040.8710000338
3057.1540000383
332
0
204
text/html
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)
442.516
7.125
650.508
11.184
682.981
7.466
845.198
18.737
988.46
7.717
1023.791
32.425
1074.945
25.768
1100.883
5.178
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Other

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Filmizilla.me should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
Properly size images
Images can slow down the page's load time. Filmizilla.me should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Filmizilla.me should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Filmizilla.me should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Filmizilla.me should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Filmizilla.me should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Reduce unused JavaScript — Potential savings of 30 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.google.com/adsense/domains/caf.js
52670
31230
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Serve images in next-gen formats
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
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.
Initial server response time was short — Root document took 120 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
http://ww25.filmizilla.me/?subid1=20220102-0151-2672-87cb-6ddb00e39949
115.928
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Filmizilla.me should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://filmizilla.me/
190
http://ww25.filmizilla.me/?subid1=20220102-0151-2672-87cb-6ddb00e39949
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Filmizilla.me 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.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers — Potential savings of 0 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
http://ww25.filmizilla.me/js/parking.2.75.3.js
113
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
Avoids enormous network payloads — Total size was 133 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.google.com/adsense/domains/caf.js
52670
https://www.google.com/adsense/domains/caf.js
52669
http://ww25.filmizilla.me/js/parking.2.75.3.js
19796
https://www.google.com/afs/ads?psid=6512503653&pcsa=false&channel=pid-bodis-gcontrol264%2Cpid-bodis-gcontrol97%2Cpid-bodis-gcontrol314%2Cpid-bodis-gcontrol152&client=dp-bodis30_3ph&r=m&hl=en&max_radlink_len=60&type=3&uiopt=true&swp=as-drid-2166691821371338&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300769%2C17300771%2C17300842%2C17300859%2C17300862&format=r3&nocache=1671641048686818&num=0&output=afd_ads&domain_name=ww25.filmizilla.me&v=3&bsl=8&pac=0&u_his=2&u_tz=-480&dt=1641048686819&u_w=800&u_h=600&biw=1350&bih=940&psw=1334&psh=77&frm=0&uio=-&cont=rs&inames=master-1&jsv=90062&rurl=http%3A%2F%2Fww25.filmizilla.me%2F%3Fsubid1%3D20220102-0151-2672-87cb-6ddb00e39949
2856
http://ww25.filmizilla.me/_fd?subid1=20220102-0151-2672-87cb-6ddb00e39949
2039
http://ww25.filmizilla.me/?subid1=20220102-0151-2672-87cb-6ddb00e39949
2002
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/call_to_action_arrow.svg?c=%23ffffff
1194
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/search.svg?c=%231967d2
1188
http://ww25.filmizilla.me/px.gif?ch=1&rn=9.539406172849729
421
http://ww25.filmizilla.me/px.gif?ch=2&rn=9.539406172849729
421
Uses efficient cache policy on static assets — 2 resources found
Filmizilla.me can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/call_to_action_arrow.svg?c=%23ffffff
82800000
1194
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/search.svg?c=%231967d2
82800000
1188
Avoids an excessive DOM size — 12 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
12
Maximum DOM Depth
5
Maximum Child Elements
5
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. Filmizilla.me 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.1 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)
https://www.google.com/adsense/domains/caf.js
66.068
43.245
4.921
http://ww25.filmizilla.me/js/parking.2.75.3.js
50.776
45.85
1.116
Minimizes main-thread work — 0.2 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
96.864
Other
35.971
Style & Layout
11.211
Script Parsing & Compilation
8.99
Parse HTML & CSS
6.48
Rendering
5.593
Garbage Collection
2.758
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 — 14 requests • 133 KiB
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
14
136330
Script
3
125135
Document
2
4858
Image
6
3888
Other
3
2449
Stylesheet
0
0
Media
0
0
Font
0
0
Third-party
7
111241
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 Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
108859
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Avoid large layout shifts — 2 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.0091223404255319
0.00053270291568164
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.
Avoid long main-thread tasks
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
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 filmizilla.me on mobile screens.

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.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.
86

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of filmizilla.me. 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.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
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.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[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 toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[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.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

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.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<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.
Links 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.
`<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>`, `<template>` or `<div>` 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.
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.

Internationalization and localization

`<html>` element has 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.
`<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.

Best practices

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

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Filmizilla.me may provide assistance to deaf or hearing-impaired users with captions on videos.

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

Names and labels

`<frame>` or `<iframe>` elements do not have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
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.
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 filmizilla.me should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

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 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 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.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

Audits

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.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 7 insecure requests 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 Request Resolution
http://filmizilla.me/
Allowed
http://ww25.filmizilla.me/?subid1=20220102-0151-2672-87cb-6ddb00e39949
Allowed
http://ww25.filmizilla.me/js/parking.2.75.3.js
Allowed
http://ww25.filmizilla.me/_fd?subid1=20220102-0151-2672-87cb-6ddb00e39949
Allowed
http://ww25.filmizilla.me/px.gif?ch=1&rn=9.539406172849729
Allowed
http://ww25.filmizilla.me/px.gif?ch=2&rn=9.539406172849729
Allowed
http://ww25.filmizilla.me/_tr
Allowed

Audits

Browser errors were logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Source Description
Failed to load resource: net::ERR_ACCESS_DENIED
TypeError: Failed to fetch at Function.value (http://ww25.filmizilla.me/js/parking.2.75.3.js:1:31091) at http://ww25.filmizilla.me/js/parking.2.75.3.js:1:58866 at s (http://ww25.filmizilla.me/js/parking.2.75.3.js:1:44714) at Generator._invoke (http://ww25.filmizilla.me/js/parking.2.75.3.js:1:44467) at Generator.forEach.e.<computed> [as next] (http://ww25.filmizilla.me/js/parking.2.75.3.js:1:45071) at m (http://ww25.filmizilla.me/js/parking.2.75.3.js:1:56400) at a (http://ww25.filmizilla.me/js/parking.2.75.3.js:1:56603) at http://ww25.filmizilla.me/js/parking.2.75.3.js:1:56662 at new Promise (<anonymous>) at http://ww25.filmizilla.me/js/parking.2.75.3.js:1:56543
90

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for filmizilla.me. 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 filmizilla.me 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.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
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.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
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.

Crawling and Indexing

Page is 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.
Blocking Directive Source

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.
22

PWA

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

PWA Optimized

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 filmizilla.me on mobile screens.

Installable

Web app manifest or service worker do not meet the installability requirements — 1 reason
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
Failure reason
No manifest was fetched

PWA Optimized

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.
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.
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

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) 76
Performance 87
Accessibility 86
Best Practices 92
SEO 83
PWA 30
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on mobile
87

Performance

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

Metrics

Time to Interactive — 3.1 s
The time taken for the page to become fully interactive.
Speed Index — 3.1 s
The time taken for the page contents to be visibly populated.
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).
Cumulative Layout Shift — 0.031
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

Max Potential First Input Delay — 20 ms
Users could experience a delay when interacting with the page.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://filmizilla.me/
http/1.1
0
269.70400009304
410
0
302
text/html
http://ww25.filmizilla.me/?subid1=20220102-0151-3708-a5e9-25d82a5893f3
http/1.1
270.00799961388
385.50799991935
1979
1889
200
text/html
Document
http://ww25.filmizilla.me/js/parking.2.75.3.js
http/1.1
396.62199933082
512.04599998891
19796
59052
200
application/javascript
Script
http://ww25.filmizilla.me/_fd?subid1=20220102-0151-3708-a5e9-25d82a5893f3
http/1.1
521.86500001699
762.55799923092
2039
2509
200
text/html
Fetch
https://www.google.com/adsense/domains/caf.js
h2
522.60100003332
534.39599927515
52682
141267
200
text/javascript
Script
http://ww25.filmizilla.me/px.gif?ch=1&rn=8.411676914384836
http/1.1
523.43400008976
647.26599957794
421
42
200
image/gif
Image
http://ww25.filmizilla.me/px.gif?ch=2&rn=8.411676914384836
http/1.1
523.69799930602
639.84499964863
421
42
200
image/gif
Image
https://www.google.com/afs/ads?psid=6512503653&pcsa=false&channel=pid-bodis-gcontrol264%2Cpid-bodis-gcontrol97%2Cpid-bodis-gcontrol314%2Cpid-bodis-gcontrol152&client=dp-bodis30_3ph&r=m&hl=en&max_radlink_len=60&type=3&uiopt=true&swp=as-drid-2166691821371338&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300003%2C17300769%2C17300771%2C17300841%2C17300863%2C17300866&format=r3&nocache=231641048697673&num=0&output=afd_ads&domain_name=ww25.filmizilla.me&v=3&bsl=8&pac=0&u_his=2&u_tz=-480&dt=1641048697674&u_w=360&u_h=640&biw=360&bih=640&psw=344&psh=77&frm=0&uio=-&cont=rs&inames=master-1&jsv=90062&rurl=http%3A%2F%2Fww25.filmizilla.me%2F%3Fsubid1%3D20220102-0151-3708-a5e9-25d82a5893f3
h2
782.23800007254
856.08099959791
2800
5631
200
text/html
Document
https://www.google.com/adsense/domains/caf.js
h2
868.74599941075
881.55799917877
52670
141240
200
text/javascript
Script
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/search.svg?c=%231967d2
h2
914.5819991827
921.6209994629
1188
391
200
image/svg+xml
Image
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/call_to_action_arrow.svg?c=%23ffffff
h2
914.73300009966
917.89699997753
1194
444
200
image/svg+xml
Image
http://ww25.filmizilla.me/_tr
http/1.1
947.34899979085
1085.6599994004
560
2
200
text/html
Fetch
https://www.google.com/afs/gen_204?client=dp-bodis30_3ph&output=uds_ads_only&zx=ajgpj3ew3ohs&aqid=eWrQYf2xLNCNoPwP7umD-A8&psid=6512503653&pbt=bs&adbx=0&adby=65.8125&adbh=451&adbw=360&adbah=145%2C145%2C145&adbn=master-1&eawp=partner-dp-bodis30_3ph&errv=9006289805167013517&csadii=11&csadr=154&csala=11%7C92%7C27%7C35&lle=0&llm=1000&ifv=1&usr=1
h2
2434.5519999042
2454.5319993049
332
0
204
text/html
Image
https://www.google.com/afs/gen_204?client=dp-bodis30_3ph&output=uds_ads_only&zx=an9dtsxcs12g&aqid=eWrQYf2xLNCNoPwP7umD-A8&psid=6512503653&pbt=bv&adbx=0&adby=65.8125&adbh=451&adbw=360&adbah=145%2C145%2C145&adbn=master-1&eawp=partner-dp-bodis30_3ph&errv=9006289805167013517&csadii=11&csadr=154&csala=11%7C92%7C27%7C35&lle=0&llm=1000&ifv=1&usr=1
h2
2935.407999903
2953.1099991873
332
0
204
text/html
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)
439.26
7.053
567.102
8.597
593.428
5.987
815.49
21.01
910.101
7.364
941.446
26.018
982.139
16.47
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Other

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Filmizilla.me should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
Properly size images
Images can slow down the page's load time. Filmizilla.me should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Filmizilla.me should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Filmizilla.me should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Filmizilla.me should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Filmizilla.me 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
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
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.
Initial server response time was short — Root document took 120 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
http://ww25.filmizilla.me/?subid1=20220102-0151-3708-a5e9-25d82a5893f3
116.494
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Filmizilla.me should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://filmizilla.me/
630
http://ww25.filmizilla.me/?subid1=20220102-0151-3708-a5e9-25d82a5893f3
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Filmizilla.me 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.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers — Potential savings of 0 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
http://ww25.filmizilla.me/js/parking.2.75.3.js
113
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
Avoids enormous network payloads — Total size was 134 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.google.com/adsense/domains/caf.js
52682
https://www.google.com/adsense/domains/caf.js
52670
http://ww25.filmizilla.me/js/parking.2.75.3.js
19796
https://www.google.com/afs/ads?psid=6512503653&pcsa=false&channel=pid-bodis-gcontrol264%2Cpid-bodis-gcontrol97%2Cpid-bodis-gcontrol314%2Cpid-bodis-gcontrol152&client=dp-bodis30_3ph&r=m&hl=en&max_radlink_len=60&type=3&uiopt=true&swp=as-drid-2166691821371338&oe=UTF-8&ie=UTF-8&fexp=21404%2C17300003%2C17300769%2C17300771%2C17300841%2C17300863%2C17300866&format=r3&nocache=231641048697673&num=0&output=afd_ads&domain_name=ww25.filmizilla.me&v=3&bsl=8&pac=0&u_his=2&u_tz=-480&dt=1641048697674&u_w=360&u_h=640&biw=360&bih=640&psw=344&psh=77&frm=0&uio=-&cont=rs&inames=master-1&jsv=90062&rurl=http%3A%2F%2Fww25.filmizilla.me%2F%3Fsubid1%3D20220102-0151-3708-a5e9-25d82a5893f3
2800
http://ww25.filmizilla.me/_fd?subid1=20220102-0151-3708-a5e9-25d82a5893f3
2039
http://ww25.filmizilla.me/?subid1=20220102-0151-3708-a5e9-25d82a5893f3
1979
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/call_to_action_arrow.svg?c=%23ffffff
1194
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/search.svg?c=%231967d2
1188
http://ww25.filmizilla.me/_tr
560
http://ww25.filmizilla.me/px.gif?ch=1&rn=8.411676914384836
421
Uses efficient cache policy on static assets — 2 resources found
Filmizilla.me can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/call_to_action_arrow.svg?c=%23ffffff
82800000
1194
https://afs.googleusercontent.com/ad_icons/standard/publisher_icon_image/search.svg?c=%231967d2
82800000
1188
Avoids an excessive DOM size — 12 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
12
Maximum DOM Depth
5
Maximum Child Elements
5
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. Filmizilla.me 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.4 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)
https://www.google.com/adsense/domains/caf.js
304.612
202.508
17.556
http://ww25.filmizilla.me/js/parking.2.75.3.js
162.184
151.492
3.784
Unattributable
76.596
2.448
0
http://ww25.filmizilla.me/?subid1=20220102-0151-3708-a5e9-25d82a5893f3
50.968
6.44
4.092
Minimizes main-thread work — 0.6 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
370.032
Other
161.412
Style & Layout
45.684
Script Parsing & Compilation
31.744
Parse HTML & CSS
19.064
Rendering
18.956
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 — 14 requests • 134 KiB
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
14
136824
Script
3
125148
Document
2
4779
Image
6
3888
Other
3
3009
Stylesheet
0
0
Media
0
0
Font
0
0
Third-party
7
111198
Minimize third-party usage — Third-party code blocked the main thread for 20 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 Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
108816
18.924
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Avoid large layout shifts — 2 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.029570770263672
0.0015234375
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.
Avoid long main-thread tasks — 1 long task found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://www.google.com/adsense/domains/caf.js
3004
104
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
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 filmizilla.me on mobile screens.

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.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Metrics

Largest Contentful Paint — 3.1 s
The timing of the largest text or image that is painted.

Audits

First Meaningful Paint — 3.1 s
The time taken for the primary content of the page to be rendered.

Other

Reduce unused JavaScript — Potential savings of 30 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.google.com/adsense/domains/caf.js
52682
31184

Metrics

First Contentful Paint — 3.1 s
The time taken for the first image or text on the page to be rendered.

Other

First Contentful Paint (3G) — 5958 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.
86

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of filmizilla.me. 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.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
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.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[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 toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[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.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

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.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<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.
Links 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.
`<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>`, `<template>` or `<div>` 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.
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.

Internationalization and localization

`<html>` element has 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.
`<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.

Best practices

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

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Filmizilla.me may provide assistance to deaf or hearing-impaired users with captions on videos.

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

Names and labels

`<frame>` or `<iframe>` elements do not have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
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.
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.
92

Best Practices

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

Audits

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 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 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.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

Audits

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.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
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.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 7 insecure requests 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 Request Resolution
http://filmizilla.me/
Allowed
http://ww25.filmizilla.me/?subid1=20220102-0151-3708-a5e9-25d82a5893f3
Allowed
http://ww25.filmizilla.me/js/parking.2.75.3.js
Allowed
http://ww25.filmizilla.me/_fd?subid1=20220102-0151-3708-a5e9-25d82a5893f3
Allowed
http://ww25.filmizilla.me/px.gif?ch=1&rn=8.411676914384836
Allowed
http://ww25.filmizilla.me/px.gif?ch=2&rn=8.411676914384836
Allowed
http://ww25.filmizilla.me/_tr
Allowed
83

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for filmizilla.me. 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 filmizilla.me on mobile screens.
Tap targets are sized appropriately — 100% 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.

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.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
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.
Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
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.

Crawling and Indexing

Page is 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.
Blocking Directive Source

Mobile Friendly

Document doesn't use legible font sizes — 53.4% 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
.privacy
31.07%
11px
.si133
15.53%
10px
53.40%
≥ 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.
30

PWA

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

PWA Optimized

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 filmizilla.me on mobile screens.

Installable

Web app manifest or service worker do not meet the installability requirements — 1 reason
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.
Failure reason
No manifest was fetched

PWA Optimized

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.
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.
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

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.247.81.52
Continent: North America
Country: Canada
Canada Flag
Region:
City:
Longitude: -79.3716
Latitude: 43.6319
Currencies: CAD
Languages: English
French

Web Hosting Provider

Name IP Address
Team Internet AG
Registration

Domain Registrant

Private Registration: No
Name:
Organization: c/o whoisproxy.com
Country: US
City:
State: VA
Post Code:
Email:
Phone:
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
Key-Systems GmbH 104.22.34.174
Security

Visitor Safety

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

SSL/TLS Certificate

Technical

DNS Lookup

A Records

Host IP Address Class TTL
filmizilla.me. 104.247.81.52 IN 600

NS Records

Host Nameserver Class TTL
filmizilla.me. ns1.parkingcrew.net. IN 3600
filmizilla.me. ns2.parkingcrew.net. IN 3600

MX Records

Priority Host Server Class TTL
5 filmizilla.me. mail.h-email.net. IN 3600

SOA Records

Domain Name Primary NS Responsible Email TTL
filmizilla.me. ns1.parkingcrew.net. hostmaster.filmizilla.me. 10800

TXT Records

Host Value Class TTL
filmizilla.me. v=spf1 IN 3600

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Server: nginx
Date: 11th February, 2023
Content-Type: text/html; charset=UTF-8
Connection: keep-alive
Vary: Accept-Encoding
X-Adblock-Key: MFwwDQYJKoZIhvcNAQEBBQADSwAwSAJBALquDFETXRn0Hr05fUP7EJT77xYnPmRbpMy4vk8KYiHnkNpednjOANJcaXDXcKQJN0nXKZJL7TciJD8AoHXK158CAwEAAQ==_AGDQP2Pb/nPqd+hCnPtkGToy3xI3mXcpGfUCf3X6lZ0LySLMaGF4EQRZPmId72dPPT8qZRjO2Dp12RMtwY43Eg==
Accept-CH: ua-mobile
Accept-CH-Lifetime: 30
X-Domain: filmizilla.me
X-Subdomain:

Whois Lookup

Created: 28th June, 2020
Changed: 12th March, 2022
Expires: 28th June, 2023
Registrar: Key-Systems GmbH
Status: ok
Nameservers: ns1.parkingcrew.net
ns2.parkingcrew.net
Owner Organization: c/o whoisproxy.com
Owner State: VA
Owner Country: US
Full Whois: Domain Name: FILMIZILLA.ME
Registry Domain ID: D425500000334268691-AGRS
Registrar WHOIS Server: whois.rrpproxy.net
Registrar URL: http://www.key-systems.net
Updated Date: 2022-12-03T09:53:38Z
Creation Date: 2020-06-28T01:35:44Z
Registry Expiry Date: 2023-06-28T01:35:44Z
Registrar Registration Expiration Date:
Registrar: Key-Systems GmbH
Registrar IANA ID: 269
Registrar Abuse Contact Email:
Registrar Abuse Contact Phone:
Reseller:
Domain Status: ok https://icann.org/epp#ok
Registrant Organization: c/o whoisproxy.com
Registrant State/Province: VA
Registrant Country: US
Name Server: NS1.PARKINGCREW.NET
Name Server: NS2.PARKINGCREW.NET
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2023-02-11T13:52:44Z <<<

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

Access to WHOIS information is provided to assist persons in determining the contents of a domain name registration record in the registry database. The data in this record is provided by The Registry Operator for informational purposes only, and accuracy is not guaranteed. This service is intended only for query-based access. You agree that you will use this data only for lawful purposes and that, under no circumstances will you use this data to (a) allow, enable, or otherwise support the transmission by e-mail, telephone, or facsimile of mass unsolicited, commercial advertising or solicitations to entities other than the data recipient's own existing customers; or (b) enable high volume, automated, electronic processes that send queries or data to the systems of Registry Operator, a Registrar, or Afilias except as reasonably necessary to register domain names or modify existing registrations. All rights reserved. Registry Operator reserves the right to modify these terms at any time. By submitting this query, you agree to abide by this policy.
The Registrar of Record identified in this output may have an RDDS service that can be queried for additional information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.

Nameservers

Name IP Address
ns1.parkingcrew.net 13.248.158.159
ns2.parkingcrew.net 76.223.21.9
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5
$938 USD 1/5
0/5

Sites hosted on the same IP address

Domain Valuation Snoop Score
0/5
$434 USD 1/5
0/5
0/5