fmovies.co

fmovies.co is SSL secured

Free website and domain report on fmovies.co

Last Updated: 15th November, 2024
Overview

Snoop Summary for fmovies.co

This is a free and comprehensive report about fmovies.co. Fmovies.co is hosted in United States on a server with an IP address of 104.31.16.4, where the local currency is USD and English is the local language. Our records indicate that fmovies.co is owned/operated by WhoisGuard, Inc.. Fmovies.co is expected to earn an estimated $119 USD per day from advertising revenue. The sale of fmovies.co would possibly be worth $87,171 USD. This figure is based on the daily revenue potential of the website over a 24 month period. Fmovies.co receives an estimated 28,234 unique visitors every day - a massive amount of traffic! This report was last updated 15th November, 2024.

About fmovies.co

Site Preview: fmovies.co fmovies.co
Title: FMovies - Watch Free Movies Online | FMovies.to
Description: FMovies is the best site to watch free movies online without downloading. Stream free movies here.
Keywords and Tags: business, english movies online., fmovies, free online movies, hd movies online for free, high quality free online movies, marketing, merchandising, online movie website, watch movies, watchfree
Related Terms: 7 fmovies, fmovies ag, fmovies alternative, fmovies org, fmovies ru, fmovies site, scarface full movie fmovies, www fmovies, www6 fmovies
Fav Icon:
Age: Over 10 years old
Domain Created: 4th March, 2014
Domain Updated: 4th January, 2020
Domain Expires: 4th February, 2021
Review

Snoop Score

3/5 (Great!)

Valuation

$87,171 USD
Note: All valuation figures are estimates.

Popularity

High
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 27,818
Alexa Reach:
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority: 0
Moz Page Authority: 0

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors: 28,234
Monthly Visitors: 859,354
Yearly Visitors: 10,305,410
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $119 USD
Monthly Revenue: $3,634 USD
Yearly Revenue: $43,580 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: fmovies.co 10
Domain Name: fmovies 7
Extension (TLD): co 2
Expiry Check:

Page Speed Analysis

Average Load Time:
Load Time Comparison:

PageSpeed Insights

Avg. (All Categories) 72
Performance 96
Accessibility 48
Best Practices 77
SEO 91
Progressive Web App 48
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://fmovies.co/
Updated: 4th September, 2020

1.76 seconds
First Contentful Paint (FCP)
49%
40%
11%

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

Simulate loading on desktop
96

Performance

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

Metrics

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

Other

First CPU Idle — 1.2 s
The time taken for the page's main thread to be quiet enough to handle input.
Max Potential First Input Delay — 70 ms
Users could experience a delay when interacting with the page.
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 fmovies.co as laggy when the latency is higher than 0.05 seconds.
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://fmovies.co/
0
347.4560000468
388
0
301
https://fmovies.co/
348.02200004924
655.9160000179
3918
15683
200
text/html
Document
https://fonts.googleapis.com/css?family=Roboto:400,300,300italic,500
703.30800005468
724.60100002354
1736
9557
200
text/css
Stylesheet
https://cdnjs.cloudflare.com/ajax/libs/font-awesome/4.7.0/css/font-awesome.min.css
703.54900002712
822.38600001438
6444
31000
200
text/css
Stylesheet
https://fmovies.co/css/app.css
703.7100000307
1160.5080000008
77203
491196
200
text/css
Stylesheet
https://www.googletagmanager.com/gtag/js?id=UA-171087745-1
1168.2350000483
1189.623000042
36368
90057
200
application/javascript
Script
https://cdnjs.cloudflare.com/ajax/libs/jquery/1.12.4/jquery.min.js
703.86300003156
818.79400002072
31185
97163
200
application/javascript
Script
https://fmovies.co/js/app.js
704.0220000199
1195.0780000188
71891
266555
200
application/javascript
Script
1231.9800000405
1232.4710000539
0
26342
200
image/png
Image
https://fonts.gstatic.com/s/roboto/v16/Hgo13k-tfSpn0qi1SFdUfZBw1xU1rKptJj_0jans920.woff2
1242.275000026
1246.0590000264
10925
10304
200
font/woff2
Font
https://cdnjs.cloudflare.com/ajax/libs/font-awesome/4.7.0/fonts/fontawesome-webfont.woff2?v=4.7.0
1242.8860000218
1373.1430000043
77969
77160
200
application/octet-stream
Font
https://fonts.gstatic.com/s/roboto/v16/oMMgfZMQthOryQo9n22dcuvvDin1pK8aKteLpeZ5c0A.woff2
1244.6990000317
1247.9330000351
10821
10200
200
font/woff2
Font
https://fonts.gstatic.com/s/roboto/v16/RxZJdnzeo3R5zSexge8UUZBw1xU1rKptJj_0jans920.woff2
1247.3440000322
1250.7790000527
10857
10236
200
font/woff2
Font
https://fonts.gstatic.com/s/roboto/v16/7m8l7TlFO-S3VkhHuR0at4gp9Q8gbYrhqGlRav_IXfk.woff2
1248.6890000291
1252.6770000113
12496
11888
200
font/woff2
Font
https://fmovies.co/user/ajax/menu-bar?ts=1599195600&_=598
1617.990000057
2204.9230000121
576
156
200
application/json
XHR
https://www.google-analytics.com/analytics.js
1633.6990000564
1647.7930000401
18966
45659
200
text/javascript
Script
https://www.google-analytics.com/j/collect?v=1&_v=j85&a=1944233719&t=pageview&_s=1&dl=https%3A%2F%2Ffmovies.co%2F&ul=en-us&de=UTF-8&dt=FMovies%20-%20Watch%20Free%20Movies%20Online%20%7C%20FMovies.to&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=IEBAAUABAAAAAC~&jid=1419244445&gjid=2075230393&cid=1723927988.1599200155&tid=UA-171087745-1&_gid=1763822645.1599200155&_r=1&gtm=2ou8q1&z=1003036785
1779.2650000192
1795.9660000051
626
1
200
text/plain
XHR
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)
773.472
24.45
807.369
12.581
1276.919
28.246
1309.84
15.396
1325.265
108.496
1436.52
40.208
1478.092
7.658
1493.98
42.42
1536.534
52.28
1590.241
135.954
1726.888
15.708
1753.192
9.524
1764.52
44.01
1810.671
72.82
1883.799
7.015
2899.61
5.768
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. Fmovies.co should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://fonts.googleapis.com/css?family=Roboto:400,300,300italic,500
1736
230
https://cdnjs.cloudflare.com/ajax/libs/font-awesome/4.7.0/css/font-awesome.min.css
6444
230
https://fmovies.co/css/app.css
77203
430
Properly size images
Images can slow down the page's load time. Fmovies.co should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Fmovies.co should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Fmovies.co should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Fmovies.co should consider minifying JS files.
Remove unused CSS — Potential savings of 54 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Fmovies.co should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://fmovies.co/css/app.css
77203
55492
Remove unused JavaScript — Potential savings of 54 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://fmovies.co/js/app.js
71891
55387
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.
Initial server response time was short — Root document took 310 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Fmovies.co should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
(Start) http://fmovies.co/
0
https://fmovies.co/
190
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Fmovies.co 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 364 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://cdnjs.cloudflare.com/ajax/libs/font-awesome/4.7.0/fonts/fontawesome-webfont.woff2?v=4.7.0
77969
https://fmovies.co/css/app.css
77203
https://fmovies.co/js/app.js
71891
https://www.googletagmanager.com/gtag/js?id=UA-171087745-1
36368
https://cdnjs.cloudflare.com/ajax/libs/jquery/1.12.4/jquery.min.js
31185
https://www.google-analytics.com/analytics.js
18966
https://fonts.gstatic.com/s/roboto/v16/7m8l7TlFO-S3VkhHuR0at4gp9Q8gbYrhqGlRav_IXfk.woff2
12496
https://fonts.gstatic.com/s/roboto/v16/Hgo13k-tfSpn0qi1SFdUfZBw1xU1rKptJj_0jans920.woff2
10925
https://fonts.gstatic.com/s/roboto/v16/RxZJdnzeo3R5zSexge8UUZBw1xU1rKptJj_0jans920.woff2
10857
https://fonts.gstatic.com/s/roboto/v16/oMMgfZMQthOryQo9n22dcuvvDin1pK8aKteLpeZ5c0A.woff2
10821
Uses efficient cache policy on static assets — 3 resources found
Fmovies.co 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://www.google-analytics.com/analytics.js
7200000
18966
https://fmovies.co/css/app.css
604800000
77203
https://fmovies.co/js/app.js
604800000
71891
Avoids an excessive DOM size — 270 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
270
Maximum DOM Depth
10
Maximum Child Elements
25
Avoid chaining critical requests — 10 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Fmovies.co 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.3 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://fmovies.co/
262.176
5.146
6.893
https://fmovies.co/js/app.js
97.658
71.636
23.624
https://cdnjs.cloudflare.com/ajax/libs/jquery/1.12.4/jquery.min.js
79.047
72.284
2.072
https://www.googletagmanager.com/gtag/js?id=UA-171087745-1
78.222
38.603
32.458
https://www.google-analytics.com/analytics.js
74.296
70.206
2.33
Unattributable
62.186
4.602
0.372
Minimizes main-thread work — 0.7 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
262.477
Style & Layout
136.22
Other
101.539
Script Parsing & Compilation
67.749
Rendering
60.109
Parse HTML & CSS
59.739
Keep request counts low and transfer sizes small — 16 requests • 364 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
16
372369
Script
4
158410
Font
5
123068
Stylesheet
3
85383
Document
1
3918
Other
3
1590
Image
0
0
Media
0
0
Third-party
11
218393
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)
19592
18.786
115598
0
46835
0
36368
0
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Avoid large layout shifts — 5 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.00071114554265657
0.0003873577991407
7.0081428946677E-5
5.1485837215256E-5
2.4980299448385E-5
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 — 4 long tasks 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-analytics.com/analytics.js
1108
73
https://fmovies.co/js/app.js
1040
68
https://fmovies.co/
392
54
https://www.googletagmanager.com/gtag/js?id=UA-171087745-1
770
52

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.

Other

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

Diagnostics

Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://fonts.gstatic.com/s/roboto/v16/Hgo13k-tfSpn0qi1SFdUfZBw1xU1rKptJj_0jans920.woff2
3.7840000004508
https://cdnjs.cloudflare.com/ajax/libs/font-awesome/4.7.0/fonts/fontawesome-webfont.woff2?v=4.7.0
130.25699998252
https://fonts.gstatic.com/s/roboto/v16/oMMgfZMQthOryQo9n22dcuvvDin1pK8aKteLpeZ5c0A.woff2
3.234000003431
https://fonts.gstatic.com/s/roboto/v16/RxZJdnzeo3R5zSexge8UUZBw1xU1rKptJj_0jans920.woff2
3.435000020545
https://fonts.gstatic.com/s/roboto/v16/7m8l7TlFO-S3VkhHuR0at4gp9Q8gbYrhqGlRav_IXfk.woff2
3.9879999822006
48

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of fmovies.co. 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.
`[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.
`[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-*]` 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.

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

Names and labels

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

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.

Audio and video

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

Names and labels

Buttons do not 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.
Failing Elements
Form elements do not have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Failing Elements

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

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

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that fmovies.co 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.

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.

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 Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
Bootstrap
3.3.6
jQuery
1.12.4
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.

Audits

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://fmovies.co/
Links to cross-origin destinations are unsafe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Includes front-end JavaScript libraries with known security vulnerabilities — 9 vulnerabilities detected
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.
Library Version Vulnerability Count Highest Severity
5
Medium
4
Medium
91

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for fmovies.co. 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 fmovies.co 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.
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.

Crawling and Indexing

Links are not 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.

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 fmovies.co. 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 fmovies.co on mobile screens.
Contains some content when JavaScript is not available
Apps should display alternative content for when JavaScript is disabled.
Provides 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.

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://fmovies.co/
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
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) 67
Performance 72
Accessibility 48
Best Practices 77
SEO 87
Progressive Web App 50
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://fmovies.co/
Updated: 4th September, 2020

1.81 seconds
First Contentful Paint (FCP)
46%
45%
9%

0.01 seconds
First Input Delay (FID)
98%
2%
0%

Simulate loading on mobile
72

Performance

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

Metrics

Total Blocking Time — 130 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
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

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 fmovies.co as laggy when the latency is higher than 0.05 seconds.
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://fmovies.co/
0
102.70400019363
390
0
301
https://fmovies.co/
103.03700016811
209.6859999001
3918
15683
200
text/html
Document
https://fonts.googleapis.com/css?family=Roboto:400,300,300italic,500
224.84100004658
241.83200020343
1799
10278
200
text/css
Stylesheet
https://cdnjs.cloudflare.com/ajax/libs/font-awesome/4.7.0/css/font-awesome.min.css
225.09199986234
337.30400027707
6444
31000
200
text/css
Stylesheet
https://fmovies.co/css/app.css
225.21599987522
464.10900028422
77203
491196
200
text/css
Stylesheet
https://www.googletagmanager.com/gtag/js?id=UA-171087745-1
424.12400012836
452.65700016171
36368
90057
200
application/javascript
Script
https://cdnjs.cloudflare.com/ajax/libs/jquery/1.12.4/jquery.min.js
225.62499996275
353.26799983159
31185
97163
200
application/javascript
Script
https://fmovies.co/js/app.js
226.09000001103
403.37500022724
71891
266555
200
application/javascript
Script
https://www.google-analytics.com/analytics.js
494.62000001222
498.48600011319
18966
45659
200
text/javascript
Script
505.74599998072
506.16500014439
0
26342
200
image/png
Image
https://cdnjs.cloudflare.com/ajax/libs/font-awesome/4.7.0/fonts/fontawesome-webfont.woff2?v=4.7.0
510.63700020313
631.28599990159
77969
77160
200
application/octet-stream
Font
https://fonts.gstatic.com/s/roboto/v16/Hgo13k-tfSpn0qi1SFdUfZBw1xU1rKptJj_0jans920.woff2
511.71300001442
515.91099984944
10925
10304
200
font/woff2
Font
https://fonts.gstatic.com/s/roboto/v16/oMMgfZMQthOryQo9n22dcuvvDin1pK8aKteLpeZ5c0A.woff2
512.87200022489
515.48400009051
10821
10200
200
font/woff2
Font
https://fonts.gstatic.com/s/roboto/v16/RxZJdnzeo3R5zSexge8UUZBw1xU1rKptJj_0jans920.woff2
513.9219998382
517.03600026667
10857
10236
200
font/woff2
Font
https://fonts.gstatic.com/s/roboto/v16/7m8l7TlFO-S3VkhHuR0at4gp9Q8gbYrhqGlRav_IXfk.woff2
514.9050001055
517.63099990785
12509
11888
200
font/woff2
Font
https://fmovies.co/user/ajax/menu-bar?ts=1599195600&_=598
607.96200018376
921.5569999069
576
156
200
application/json
XHR
https://www.google-analytics.com/j/collect?v=1&_v=j85&a=239433966&t=pageview&_s=1&dl=https%3A%2F%2Ffmovies.co%2F&ul=en-us&de=UTF-8&dt=FMovies%20-%20Watch%20Free%20Movies%20Online%20%7C%20FMovies.to&sd=24-bit&sr=360x640&vp=360x640&je=0&_u=IEBAAUABAAAAAC~&jid=171176823&gjid=1023317105&cid=1231438130.1599200167&tid=UA-171087745-1&_gid=838454104.1599200167&_r=1&gtm=2ou8q1&z=1585334499
657.33799990267
660.82300012931
626
1
200
text/plain
XHR
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)
245.764
9.379
493.843
6.467
501.985
15.752
517.773
11.589
529.378
42.373
571.89
79.291
656.813
10.112
669.555
21.77
692.985
14.455
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Opportunities

Properly size images
Images can slow down the page's load time. Fmovies.co should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Fmovies.co should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Fmovies.co should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Fmovies.co should consider minifying JS files.
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.
Initial server response time was short — Root document took 110 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Fmovies.co should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
(Start) http://fmovies.co/
0
https://fmovies.co/
630
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Fmovies.co 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 364 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://cdnjs.cloudflare.com/ajax/libs/font-awesome/4.7.0/fonts/fontawesome-webfont.woff2?v=4.7.0
77969
https://fmovies.co/css/app.css
77203
https://fmovies.co/js/app.js
71891
https://www.googletagmanager.com/gtag/js?id=UA-171087745-1
36368
https://cdnjs.cloudflare.com/ajax/libs/jquery/1.12.4/jquery.min.js
31185
https://www.google-analytics.com/analytics.js
18966
https://fonts.gstatic.com/s/roboto/v16/7m8l7TlFO-S3VkhHuR0at4gp9Q8gbYrhqGlRav_IXfk.woff2
12509
https://fonts.gstatic.com/s/roboto/v16/Hgo13k-tfSpn0qi1SFdUfZBw1xU1rKptJj_0jans920.woff2
10925
https://fonts.gstatic.com/s/roboto/v16/RxZJdnzeo3R5zSexge8UUZBw1xU1rKptJj_0jans920.woff2
10857
https://fonts.gstatic.com/s/roboto/v16/oMMgfZMQthOryQo9n22dcuvvDin1pK8aKteLpeZ5c0A.woff2
10821
Uses efficient cache policy on static assets — 3 resources found
Fmovies.co 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://www.google-analytics.com/analytics.js
7200000
18966
https://fmovies.co/css/app.css
604800000
77203
https://fmovies.co/js/app.js
604800000
71891
Avoids an excessive DOM size — 270 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
270
Maximum DOM Depth
10
Maximum Child Elements
25
Avoid chaining critical requests — 10 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Fmovies.co 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.5 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://fmovies.co/
364.268
52.848
4.948
https://cdnjs.cloudflare.com/ajax/libs/jquery/1.12.4/jquery.min.js
168.868
151.86
6.652
https://fmovies.co/js/app.js
154.976
130.42
24.556
https://www.google-analytics.com/analytics.js
91.808
81.432
4.672
Unattributable
81.48
3.668
0.516
https://www.googletagmanager.com/gtag/js?id=UA-171087745-1
63.512
23.476
8.86
https://fmovies.co/css/app.css
63.008
0
0
Minimizes main-thread work — 1.0 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
443.704
Style & Layout
217.644
Other
172.004
Parse HTML & CSS
97.636
Script Parsing & Compilation
50.204
Rendering
25.38
Keep request counts low and transfer sizes small — 16 requests • 364 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
16
372447
Script
4
158410
Font
5
123081
Stylesheet
3
85446
Document
1
3918
Other
3
1592
Image
0
0
Media
0
0
Third-party
11
218469
Minimize third-party usage — Third-party code blocked the main thread for 60 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)
115598
33.484
19592
28.144
46911
0
36368
0
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Avoid large layout shifts
Below is a list of all DOM elements that contribute to the CLS of the page.
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 — 4 long tasks 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://cdnjs.cloudflare.com/ajax/libs/jquery/1.12.4/jquery.min.js
4620
159
https://www.google-analytics.com/analytics.js
4170
87
https://fmovies.co/
1121
85
https://fmovies.co/css/app.css
3690
63

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

First Contentful Paint — 3.8 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 3.8 s
The time taken for the page contents to be visibly populated.
Time to Interactive — 4.7 s
The time taken for the page to become fully interactive.

Other

First CPU Idle — 4.6 s
The time taken for the page's main thread to be quiet enough to handle input.
Max Potential First Input Delay — 160 ms
Users could experience a delay when interacting with the page.

Opportunities

Eliminate render-blocking resources — Potential savings of 630 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Fmovies.co should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://fonts.googleapis.com/css?family=Roboto:400,300,300italic,500
1799
930
https://cdnjs.cloudflare.com/ajax/libs/font-awesome/4.7.0/css/font-awesome.min.css
6444
1080
https://fmovies.co/css/app.css
77203
2430
Remove unused CSS — Potential savings of 54 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Fmovies.co should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://fmovies.co/css/app.css
77203
55776
Remove unused JavaScript — Potential savings of 54 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://fmovies.co/js/app.js
71891
55387

Metrics

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

Other

First Meaningful Paint — 4.1 s
The time taken for the primary content of the page to be rendered.
First Contentful Paint (3G) — 7914 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.

Diagnostics

Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://cdnjs.cloudflare.com/ajax/libs/font-awesome/4.7.0/fonts/fontawesome-webfont.woff2?v=4.7.0
120.64899969846
https://fonts.gstatic.com/s/roboto/v16/Hgo13k-tfSpn0qi1SFdUfZBw1xU1rKptJj_0jans920.woff2
4.1979998350143
https://fonts.gstatic.com/s/roboto/v16/oMMgfZMQthOryQo9n22dcuvvDin1pK8aKteLpeZ5c0A.woff2
2.6119998656213
https://fonts.gstatic.com/s/roboto/v16/RxZJdnzeo3R5zSexge8UUZBw1xU1rKptJj_0jans920.woff2
3.114000428468
https://fonts.gstatic.com/s/roboto/v16/7m8l7TlFO-S3VkhHuR0at4gp9Q8gbYrhqGlRav_IXfk.woff2
2.725999802351
48

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of fmovies.co. 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.
`[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.
`[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-*]` 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.

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

Names and labels

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

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.

Audio and video

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

Names and labels

Buttons do not 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.
Failing Elements
Form elements do not have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Failing Elements

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

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

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that fmovies.co 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.

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.

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 Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
Bootstrap
3.3.6
jQuery
1.12.4
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.

Audits

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://fmovies.co/
Links to cross-origin destinations are unsafe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Includes front-end JavaScript libraries with known security vulnerabilities — 9 vulnerabilities detected
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.
Library Version Vulnerability Count Highest Severity
5
Medium
4
Medium
87

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for fmovies.co. 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 fmovies.co on mobile screens.
Document uses legible font sizes — 81.64% 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
#footer .small
14.89%
10.4px
#header #logo a
3.47%
0px
81.64%
≥ 12px

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

Crawling and Indexing

Links are not 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.

Mobile Friendly

Tap targets are not sized appropriately — 29% 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
FAQ
23x15
25x15
29x15
29x15
33x15
36x15
40x15
41x15
41x15
44x15
32x15
37x15
56x15

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

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 fmovies.co. 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 fmovies.co on mobile screens.
Contains some content when JavaScript is not available
Apps should display alternative content for when JavaScript is disabled.
Provides 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.

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://fmovies.co/
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
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.31.16.4
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: No
Name:
Organization: WhoisGuard, Inc.
Country: PA
City:
State: Panama
Post Code:
Email:
Phone:
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
.CO Internet, S.A.S. 141.193.213.20
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

Issued To: sni.cloudflaressl.com
Issued By: Cloudflare Inc ECC CA-3
Valid From: 4th August, 2020
Valid To: 4th August, 2021
Subject: CN = sni.cloudflaressl.com
O = Cloudflare, Inc.
L = San Francisco
S = US
Hash: 4d04c09a
Issuer: CN = Cloudflare Inc ECC CA-3
O = Cloudflare, Inc.
S = US
Version: 2
Serial Number: 2546424058834029549730369343930443199
Serial Number (Hex): 01EA6C6635C6197BD67D6B1DB76325BF
Valid From: 4th August, 2024
Valid To: 4th August, 2024
Signature Algorithm (Short Name): ecdsa-with-SHA256
Signature Algorithm (Long Name): ecdsa-with-SHA256
Authority Key Identifier: keyid:A5:CE:37:EA:EB:B0:75:0E:94:67:88:B4:45:FA:D9:24:10:87:96:1F
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
CRL Distribution Points:
Full Name:
URI:http://crl3.digicert.com/CloudflareIncECCCA-3.crl

Full Name:
URI:http://crl4.digicert.com/CloudflareIncECCCA-3.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-3.crt

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : F6:5C:94:2F:D1:77:30:22:14:54:18:08:30:94:56:8E:
E3:4D:13:19:33:BF:DF:0C:2F:20:0B:CC:4E:F1:64:E3
Timestamp : Aug 4 16:38:28.465 2020 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:9C:B6:A3:B0:E7:9D:71:AB:3B:75:C0:
DC:D5:7C:0A:0D:9F:1C:E9:3F:67:BF:7B:55:BC:26:44:
BD:80:16:3C:9A:02:21:00:B6:37:2C:D0:E1:42:9A:FE:
17:B6:3F:27:51:83:B2:C1:E0:C3:27:5B:D3:08:1B:45:
F7:2F:AF:77:C1:1F:79:78
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 5C:DC:43:92:FE:E6:AB:45:44:B1:5E:9A:D4:56:E6:10:
37:FB:D5:FA:47:DC:A1:73:94:B2:5E:E6:F6:C7:0E:CA
Timestamp : Aug 4 16:38:28.514 2020 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:10:03:DD:CD:86:4D:6F:D9:8F:55:E2:DD:
7C:16:79:F5:8B:F7:90:AA:EF:9B:99:EC:F9:AF:7E:16:
02:F8:DD:BC:02:20:5E:C5:7F:41:BC:87:01:BB:1F:C8:
F1:0A:BD:4A:05:AA:D5:59:15:6C:14:65:C7:89:B1:62:
05:45:0E:EE:BD:20
Key Usage: Digital Signature
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:fmovies.co
DNS:sni.cloudflaressl.com
DNS:*.fmovies.co
Technical

DNS Lookup

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Date: 4th September, 2020
Content-Type: text/html; charset=utf-8
Expires: 4th September, 2020
Cache-Control: max-age=3600
Server: cloudflare
Connection: keep-alive
Set-Cookie: *
CF-Cache-Status: HIT
Age: 2149
Accept-Ranges: bytes
cf-request-id: 04f95ad5b9000015a36fae7200000001
Expect-CT: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
CF-RAY: 5cd59402ce7515a3-EWR

Whois Lookup

Created: 4th March, 2014
Changed: 4th January, 2020
Expires: 4th February, 2021
Registrar: NameCheap, Inc.
Status: ok
Nameservers: kolton.ns.cloudflare.com
sydney.ns.cloudflare.com
Owner Organization: WhoisGuard, Inc.
Owner State: Panama
Owner Country: PA
Owner Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Admin Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Tech Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Full Whois: Domain Name: fmovies.co
Registry Domain ID: D55555965-CO
Registrar WHOIS Server: whois.namecheap.com
Registrar URL: http://www.namecheap.com
Updated Date: 2020-04-01T21:22:47Z
Creation Date: 2014-04-03T11:27:06Z
Registry Expiry Date: 2021-04-02T23:59:59Z
Registrar: NameCheap, Inc.
Registrar IANA ID: 1068
Registrar Abuse Contact Email: abuse@namecheap.com
Registrar Abuse Contact Phone: +1.6613102107
Domain Status: ok https://icann.org/epp#ok
Registry Registrant ID:
Registrant Name:
Registrant Organization: WhoisGuard, Inc.
Registrant Street:
Registrant Street:
Registrant Street:
Registrant City:
Registrant State/Province: Panama
Registrant Postal Code:
Registrant Country: PA
Registrant Phone:
Registrant Phone Ext:
Registrant Fax:
Registrant Fax Ext:
Registrant Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Registry Admin ID:
Admin Name:
Admin Organization:
Admin Street:
Admin Street:
Admin Street:
Admin City:
Admin State/Province:
Admin Postal Code:
Admin Country:
Admin Phone:
Admin Phone Ext:
Admin Fax:
Admin Fax Ext:
Admin Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Registry Tech ID:
Tech Name:
Tech Organization:
Tech Street:
Tech Street:
Tech Street:
Tech City:
Tech State/Province:
Tech Postal Code:
Tech Country:
Tech Phone:
Tech Phone Ext:
Tech Fax:
Tech Fax Ext:
Tech Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Name Server: hassan.ns.cloudflare.com
Name Server: kay.ns.cloudflare.com
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2020-09-04T06:15:50Z <<<

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

The above WHOIS results have been redacted to remove potential personal data. The full WHOIS output may be available to individuals and organisations with a legitimate interest in accessing this data not outweighed by the fundamental privacy rights of the data subject. To find out more, or to make a request for access, please visit: RDDSrequest.nic.co.

.CO Internet, S.A.S., the Administrator for .CO, has collected this information for the WHOIS database through Accredited Registrars. This information is provided to you for informational purposes only and is designed to assist persons in determining contents of a domain name registration record in the .CO Internet registry database. .CO Internet makes this information available to you "as is" and does not guarantee its accuracy.

By submitting a WHOIS query, you agree that you will use this data only for lawful purposes and that, under no circumstances will you use this data: (1) to allow, enable, or otherwise support the transmission of mass unsolicited, commercial advertising or solicitations via direct mail, electronic mail, or by telephone; (2) in contravention of any applicable data and privacy protection laws; or (3) to enable high volume, automated, electronic processes that apply to the registry (or its systems). Compilation, repackaging, dissemination, or other use of the WHOIS database in its entirety, or of a substantial portion thereof, is not allowed without .CO Internet's prior written permission. .CO Internet reserves the right to modify or change these conditions at any time without prior or subsequent notification of any kind. By executing this query, in any manner whatsoever, you agree to abide by these terms. In some limited cases, domains that might appear as available in whois might not actually be available as they could be already registered and the whois not yet updated and/or they could be part of the Restricted list. In this cases, performing a check through your Registrar's (EPP check) will give you the actual status of the domain. Additionally, domains currently or previously used as extensions in 3rd level domains will not be available for registration in the 2nd level. For example, org.co, mil.co, edu.co, com.co, net.co, nom.co, arts.co, firm.co, info.co, int.co, web.co, rec.co, co.co.

NOTE: FAILURE TO LOCATE A RECORD IN THE WHOIS DATABASE IS NOT INDICATIVE OF THE AVAILABILITY OF A DOMAIN NAME. All domain names are subject to certain additional domain name registration rules. For details, please visit our site at www.cointernet.co <http://www.cointernet.co>.

Nameservers

Name IP Address
kolton.ns.cloudflare.com 172.64.35.25
sydney.ns.cloudflare.com 108.162.194.102
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5
$1,897 USD 2/5
0/5
$686 USD 1/5
$2,634 USD 2/5

Sites hosted on the same IP address