fmovies.se

fmovies.se is SSL secured

Free website and domain report on fmovies.se

Last Updated: 6th June, 2021 Update Now
Overview

Snoop Summary for fmovies.se

This is a free and comprehensive report about fmovies.se. Fmovies.se is hosted in Canada on a server with an IP address of 104.247.81.74, where CAD is the local currency and the local language is English. Fmovies.se has the potential to be earning an estimated $4 USD per day from advertising revenue. If fmovies.se was to be sold it would possibly be worth $3,181 USD (based on the daily revenue potential of the website over a 24 month period). Fmovies.se receives an estimated 1,524 unique visitors every day - a large amount of traffic! This report was last updated 6th June, 2021.

About fmovies.se

Site Preview:
Title: fmovies.se
Description:
Keywords and Tags: potential illegal software
Related Terms: 7 fmovies, fmovies ag, fmovies alternative, fmovies org, fmovies ru, fmovies site, fmovies.to, www fmovies, www6 fmovies, www7 fmovies to
Fav Icon:
Age: Over 6 years old
Domain Created: 10th November, 2018
Domain Updated: 28th February, 2021
Domain Expires: 10th November, 2023
Review

Snoop Score

2/5

Valuation

$3,181 USD
Note: All valuation figures are estimates.

Popularity

Modest
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 536,187
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: 1,524
Monthly Visitors: 46,386
Yearly Visitors: 556,260
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $4 USD
Monthly Revenue: $132 USD
Yearly Revenue: $1,585 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.se 10
Domain Name: fmovies 7
Extension (TLD): se 2
Expiry Check:

Page Speed Analysis

Average Load Time: 2.02 seconds
Load Time Comparison: Faster than 44% of sites

PageSpeed Insights

Avg. (All Categories) 61
Performance 0
Accessibility 59
Best Practices 87
SEO 80
Progressive Web App 18
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
0

Performance

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

Opportunities

Initial server response time was short — Root document took 370 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://fmovies.se/
374.491

Diagnostics

Avoids enormous network payloads — Total size was 259 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
http://i2.cdn-image.com/__media__/pics/12471/bodybg.png
97502
http://i2.cdn-image.com/__media__/fonts/ubuntu-b/ubuntu-b.woff
38206
http://i2.cdn-image.com/__media__/pics/12471/kwbg.jpg
37532
http://i2.cdn-image.com/__media__/fonts/ubuntu-r/ubuntu-r.woff
37430
https://pxlgnpgecom-a.akamaihd.net/javascripts/browserfp.min.js?templateId=10&customerId=9CUO250V9
34340
http://iyfnz.com/?dn=fmovies.se&pid=9PO755G95
6240
http://i2.cdn-image.com/__media__/pics/12471/logo.png
4266
http://i2.cdn-image.com/__media__/js/min.js?v2.2
3417
http://i2.cdn-image.com/__media__/pics/12471/libg.png
1402
http://i2.cdn-image.com/__media__/pics/12471/arrow.png
1370
Avoids an excessive DOM size — 3 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
3
Maximum DOM Depth
3
Maximum Child Elements
2
Keep request counts low and transfer sizes small — 16 requests • 259 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
265574
Image
5
142072
Font
2
75636
Script
4
39013
Document
2
6932
Stylesheet
2
1518
Other
1
403
Media
0
0
Third-party
15
264882
Largest Contentful Paint element — 0 elements found
The element which was identified as the Largest Contentful Paint.
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
2.7948515891778E-5
2.7948515891778E-5
2.7948515891778E-5
2.7948515891778E-5
2.7948515891778E-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 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.

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.

Other

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://fmovies.se/
http/1.1
0
373.49400017411
692
840
200
text/html
Document
http://d1lxhc4jvstzrp.cloudfront.net/themes/assets/style.css
http/1.1
383.8860001415
423.81899990141
827
829
200
text/css
Stylesheet
http://d1lxhc4jvstzrp.cloudfront.net/themes/assets/skenzo.css
http/1.1
384.10799996927
399.74100003019
691
345
200
text/css
Stylesheet
http://iyfnz.com/?dn=fmovies.se&pid=9PO755G95
http/1.1
386.8829999119
615.87399989367
6240
21699
200
text/html
Document
http://iyfnz.com/px.js?ch=1
http/1.1
626.46599998698
787.60599996895
628
346
200
application/javascript
Script
http://iyfnz.com/px.js?ch=2
http/1.1
626.71100022271
3591.0169999115
628
346
200
application/javascript
Script
http://i2.cdn-image.com/__media__/js/min.js?v2.2
http/1.1
626.97499990463
872.29599989951
3417
8477
200
application/javascript
Script
http://i2.cdn-image.com/__media__/pics/12471/bodybg.png
http/1.1
3596.97900014
3850.3979998641
97502
97189
200
image/png
Image
http://i2.cdn-image.com/__media__/pics/12471/logo.png
http/1.1
3597.2540001385
3619.2689999007
4266
3956
200
image/png
Image
http://i2.cdn-image.com/__media__/pics/12471/kwbg.jpg
http/1.1
3597.6419998333
3622.3969999701
37532
37219
200
image/jpeg
Image
http://i2.cdn-image.com/__media__/pics/12471/libg.png
http/1.1
3598.0540001765
3639.5260002464
1402
1092
200
image/png
Image
http://i2.cdn-image.com/__media__/pics/12471/arrow.png
http/1.1
3598.4330000356
3790.9679999575
1370
1060
200
image/png
Image
http://i2.cdn-image.com/__media__/fonts/ubuntu-r/ubuntu-r.woff
http/1.1
3599.0760000423
3764.3289999105
37430
37152
200
application/font-woff
Font
http://i2.cdn-image.com/__media__/fonts/ubuntu-b/ubuntu-b.woff
http/1.1
3599.3969999254
3714.081000071
38206
37928
200
application/font-woff
Font
http://pxlgnpgecom-a.akamaihd.net/javascripts/browserfp.min.js?templateId=10&customerId=9CUO250V9
http/1.1
3608.9320001192
3746.0039998405
403
0
301
text/html
https://pxlgnpgecom-a.akamaihd.net/javascripts/browserfp.min.js?templateId=10&customerId=9CUO250V9
http/1.1
3746.3739998639
3948.1319999322
34340
110227
200
text/javascript
Script
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.
Script Treemap Data
Provide as required, for treemap app.

Metrics

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

Other

Max Potential First Input Delay
Users could experience a delay when interacting with the page.
First Meaningful Paint
The time taken for the primary content of the page to be rendered.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Diagnostics
Below is a collection of useful page vitals.
Metrics
Below is a collection of metrics.

Opportunities

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Fmovies.se 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. Fmovies.se should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Fmovies.se should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Fmovies.se should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Fmovies.se should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Fmovies.se should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Reduce unused JavaScript
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
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.
Avoid multiple page redirects
Redirects can cause additional delays before the page can begin loading. Fmovies.se should avoid multiple or unnecessary page redirects.
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Fmovies.se 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
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.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.

Diagnostics

Serve static assets with an efficient cache policy — 13 resources found
Fmovies.se 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)
http://i2.cdn-image.com/__media__/fonts/ubuntu-b/ubuntu-b.woff
0
38206
http://i2.cdn-image.com/__media__/fonts/ubuntu-r/ubuntu-r.woff
0
37430
http://d1lxhc4jvstzrp.cloudfront.net/themes/assets/style.css
0
827
http://d1lxhc4jvstzrp.cloudfront.net/themes/assets/skenzo.css
0
691
http://iyfnz.com/px.js?ch=1
0
628
http://iyfnz.com/px.js?ch=2
0
628
https://pxlgnpgecom-a.akamaihd.net/javascripts/browserfp.min.js?templateId=10&customerId=9CUO250V9
1800000
34340
http://i2.cdn-image.com/__media__/pics/12471/libg.png
16981000
1402
http://i2.cdn-image.com/__media__/pics/12471/kwbg.jpg
17018000
37532
http://i2.cdn-image.com/__media__/pics/12471/logo.png
52017000
4266
http://i2.cdn-image.com/__media__/pics/12471/arrow.png
75738000
1370
http://i2.cdn-image.com/__media__/pics/12471/bodybg.png
81420000
97502
http://i2.cdn-image.com/__media__/js/min.js?v2.2
84222000
3417
Avoid chaining critical requests
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Fmovies.se 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
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.
Minimizes main-thread work
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.
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)
http://i2.cdn-image.com/__media__/fonts/ubuntu-r/ubuntu-r.woff
165.25299986824
http://i2.cdn-image.com/__media__/fonts/ubuntu-b/ubuntu-b.woff
114.68400014564
Minimize third-party usage
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
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.

Budgets

Timing budget
It is advised to set a timing budget to monitor the performance of your site.
59

Accessibility

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

Contrast

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

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.

Audio and video

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

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

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

Best Practices

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

Audits

Links to cross-origin destinations are safe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids 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

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.
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.
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 — 15 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://fmovies.se/
Allowed
http://d1lxhc4jvstzrp.cloudfront.net/themes/assets/style.css
Allowed
http://d1lxhc4jvstzrp.cloudfront.net/themes/assets/skenzo.css
Allowed
http://iyfnz.com/?dn=fmovies.se&pid=9PO755G95
Allowed
http://iyfnz.com/px.js?ch=1
Allowed
http://iyfnz.com/px.js?ch=2
Allowed
http://i2.cdn-image.com/__media__/js/min.js?v2.2
Allowed
http://i2.cdn-image.com/__media__/pics/12471/bodybg.png
Allowed
http://i2.cdn-image.com/__media__/pics/12471/logo.png
Allowed
http://i2.cdn-image.com/__media__/pics/12471/kwbg.jpg
Allowed
http://i2.cdn-image.com/__media__/pics/12471/libg.png
Allowed
http://i2.cdn-image.com/__media__/pics/12471/arrow.png
Allowed
http://i2.cdn-image.com/__media__/fonts/ubuntu-r/ubuntu-r.woff
Allowed
http://i2.cdn-image.com/__media__/fonts/ubuntu-b/ubuntu-b.woff
Allowed
http://pxlgnpgecom-a.akamaihd.net/javascripts/browserfp.min.js?templateId=10&customerId=9CUO250V9
Allowed

Audits

Page lacks the HTML doctype, thus triggering quirks-mode
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
80

SEO

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

Content Best Practices

Document does not have 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.

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

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.se. 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 fmovies.se 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.
Does not redirect HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
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 0
Accessibility 59
Best Practices 87
SEO 83
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
0

Performance

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

Opportunities

Initial server response time was short — Root document took 300 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://fmovies.se/
296.072

Diagnostics

Avoids enormous network payloads — Total size was 107 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://pxlgnpgecom-a.akamaihd.net/javascripts/browserfp.min.js?templateId=10&customerId=9CUO250V9
34344
http://i1.cdn-image.com/__media__/fonts/montserrat-medium/montserrat-medium.woff
33594
http://i1.cdn-image.com/__media__/fonts/poppins-medium/poppins-medium.woff
23534
http://iyfnz.com/?dn=fmovies.se&pid=9PO755G95
8677
http://i1.cdn-image.com/__media__/js/min.js?v2.2
3417
http://i1.cdn-image.com/__media__/pics/28211/transarrow.png
1212
http://i1.cdn-image.com/__media__/pics/28211/search-11.png
1150
http://d1lxhc4jvstzrp.cloudfront.net/themes/assets/style.css
827
http://fmovies.se/
692
http://d1lxhc4jvstzrp.cloudfront.net/themes/assets/skenzo.css
691
Avoids an excessive DOM size — 3 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
3
Maximum DOM Depth
3
Maximum Child Elements
2
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 13 requests • 107 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
13
109786
Font
2
57128
Script
4
39017
Document
2
9369
Image
2
2362
Stylesheet
2
1518
Other
1
392
Media
0
0
Third-party
12
109094
Largest Contentful Paint element — 0 elements found
The element which was identified as 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.0027037938435872
0.0012343406677246
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 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.

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.

Other

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://fmovies.se/
http/1.1
0
295.07500026375
692
840
200
text/html
Document
http://d1lxhc4jvstzrp.cloudfront.net/themes/assets/style.css
http/1.1
312.13499978185
353.5390002653
827
829
200
text/css
Stylesheet
http://d1lxhc4jvstzrp.cloudfront.net/themes/assets/skenzo.css
http/1.1
312.5229999423
340.97000025213
691
345
200
text/css
Stylesheet
http://iyfnz.com/?dn=fmovies.se&pid=9PO755G95
http/1.1
316.25699996948
887.58200034499
8677
35143
200
text/html
Document
http://iyfnz.com/px.js?ch=1
http/1.1
903.76400016248
950.35899989307
628
346
200
application/javascript
Script
http://iyfnz.com/px.js?ch=2
http/1.1
903.99000048637
991.52300041169
628
346
200
application/javascript
Script
http://i1.cdn-image.com/__media__/js/min.js?v2.2
http/1.1
904.19600065798
949.3240006268
3417
8477
200
application/javascript
Script
http://i1.cdn-image.com/__media__/pics/28211/transarrow.png
http/1.1
1000.9320005774
1023.2939999551
1212
903
200
image/png
Image
http://i1.cdn-image.com/__media__/pics/28211/search-11.png
http/1.1
1002.3800004274
1134.0310005471
1150
841
200
image/png
Image
http://i1.cdn-image.com/__media__/fonts/montserrat-medium/montserrat-medium.woff
http/1.1
1002.6900004596
1051.0330004618
33594
33316
200
application/font-woff
Font
http://i1.cdn-image.com/__media__/fonts/poppins-medium/poppins-medium.woff
http/1.1
1003.2259998843
1117.9490005597
23534
23256
200
application/font-woff
Font
http://pxlgnpgecom-a.akamaihd.net/javascripts/browserfp.min.js?templateId=10&customerId=9CUO250V9
http/1.1
1026.8740002066
1138.4200006723
392
0
301
text/html
https://pxlgnpgecom-a.akamaihd.net/javascripts/browserfp.min.js?templateId=10&customerId=9CUO250V9
http/1.1
1138.8410003856
1262.9380002618
34344
110231
200
text/javascript
Script
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.
Script Treemap Data
Provide as required, for treemap app.

Diagnostics

Serve static assets with an efficient cache policy — 10 resources found
Fmovies.se 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)
http://i1.cdn-image.com/__media__/fonts/montserrat-medium/montserrat-medium.woff
0
33594
http://i1.cdn-image.com/__media__/fonts/poppins-medium/poppins-medium.woff
0
23534
http://d1lxhc4jvstzrp.cloudfront.net/themes/assets/style.css
0
827
http://d1lxhc4jvstzrp.cloudfront.net/themes/assets/skenzo.css
0
691
http://iyfnz.com/px.js?ch=1
0
628
http://iyfnz.com/px.js?ch=2
0
628
https://pxlgnpgecom-a.akamaihd.net/javascripts/browserfp.min.js?templateId=10&customerId=9CUO250V9
1800000
34344
http://i1.cdn-image.com/__media__/js/min.js?v2.2
42137000
3417
http://i1.cdn-image.com/__media__/pics/28211/transarrow.png
76574000
1212
http://i1.cdn-image.com/__media__/pics/28211/search-11.png
77931000
1150

Metrics

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

Other

Max Potential First Input Delay
Users could experience a delay when interacting with the page.
First Meaningful Paint
The time taken for the primary content of the page to be rendered.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Diagnostics
Below is a collection of useful page vitals.
Metrics
Below is a collection of metrics.
First Contentful Paint (3G)
The time taken for the first image or text on the page to be rendered while on a 3G network.

Opportunities

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Fmovies.se 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. Fmovies.se should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Fmovies.se should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Fmovies.se should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Fmovies.se should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Fmovies.se should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
Reduce unused JavaScript
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
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.
Avoid multiple page redirects
Redirects can cause additional delays before the page can begin loading. Fmovies.se should avoid multiple or unnecessary page redirects.
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Fmovies.se 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
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.
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.

Diagnostics

Avoid chaining critical requests
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Fmovies.se 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
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.
Minimizes main-thread work
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.
Minimize third-party usage
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
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.

Budgets

Timing budget
It is advised to set a timing budget to monitor the performance of your site.
59

Accessibility

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

Contrast

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

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.

Audio and video

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

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

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

Best Practices

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

Audits

Links to cross-origin destinations are safe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids 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

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.
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.
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 — 12 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://fmovies.se/
Allowed
http://d1lxhc4jvstzrp.cloudfront.net/themes/assets/style.css
Allowed
http://d1lxhc4jvstzrp.cloudfront.net/themes/assets/skenzo.css
Allowed
http://iyfnz.com/?dn=fmovies.se&pid=9PO755G95
Allowed
http://iyfnz.com/px.js?ch=1
Allowed
http://iyfnz.com/px.js?ch=2
Allowed
http://i1.cdn-image.com/__media__/js/min.js?v2.2
Allowed
http://i1.cdn-image.com/__media__/pics/28211/transarrow.png
Allowed
http://i1.cdn-image.com/__media__/pics/28211/search-11.png
Allowed
http://i1.cdn-image.com/__media__/fonts/montserrat-medium/montserrat-medium.woff
Allowed
http://i1.cdn-image.com/__media__/fonts/poppins-medium/poppins-medium.woff
Allowed
http://pxlgnpgecom-a.akamaihd.net/javascripts/browserfp.min.js?templateId=10&customerId=9CUO250V9
Allowed

Audits

Page lacks the HTML doctype, thus triggering quirks-mode
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
83

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for fmovies.se. 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.se on mobile screens.
Document uses legible font sizes — 100% 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
100.00%
≥ 12px
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.
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.

Content Best Practices

Document does not have 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.

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

Server Location

Server IP Address: 104.247.81.74
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:
Country:
City:
State:
Post Code:
Email:
Phone:
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Security

Visitor Safety

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

SSL/TLS Certificate

Issued To: fmovies.se
Issued By: Sectigo RSA Domain Validation Secure Server CA
Valid From: 16th April, 2019
Valid To: 15th April, 2020
Subject: CN = fmovies.se
Hash: 1ff11286
Issuer: CN = Sectigo RSA Domain Validation Secure Server CA
O = Sectigo Limited
S = GB
Version: 2
Serial Number: 0xC6C71A7438A71BEFB245ED2A7C1EB721
Serial Number (Hex): C6C71A7438A71BEFB245ED2A7C1EB721
Valid From: 16th April, 2024
Valid To: 15th April, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:8D:8C:5E:C4:54:AD:8A:E1:77:E9:9B:F9:9B:05:E1:B8:01:8D:61:E1
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
Certificate Policies: Policy: 1.3.6.1.4.1.6449.1.2.2.7
CPS: https://sectigo.com/CPS
Policy: 2.23.140.1.2.1

Authority Information Access: CA Issuers - URI:http://crt.sectigo.com/SectigoRSADomainValidationSecureServerCA.crt
OCSP - URI:http://ocsp.sectigo.com

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : BB:D9:DF:BC:1F:8A:71:B5:93:94:23:97:AA:92:7B:47:
38:57:95:0A:AB:52:E8:1A:90:96:64:36:8E:1E:D1:85
Timestamp : Apr 16 11:03:48.330 2019 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:51:6F:B3:E9:8C:E4:40:39:33:AC:20:5C:
B9:C0:F0:A6:29:F2:3E:C0:FB:74:FE:3F:5A:A6:EC:1D:
7F:39:46:FC:02:20:5D:95:BB:07:E1:7D:06:3D:00:0C:
70:A4:41:43:EA:90:3F:98:24:D0:15:76:35:95:67:97:
CC:F2:C2:97:21:35
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 5E:A7:73:F9:DF:56:C0:E7:B5:36:48:7D:D0:49:E0:32:
7A:91:9A:0C:84:A1:12:12:84:18:75:96:81:71:45:58
Timestamp : Apr 16 11:03:48.325 2019 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:20:55:75:F6:D2:56:2D:B9:BE:A7:69:4B:35:
03:72:1A:42:BE:DC:BD:7B:B9:22:6D:DC:5C:97:68:AE:
58:14:A5:6E:02:21:00:88:4B:16:6A:05:A0:7C:2D:2C:
50:EF:68:1C:C1:1F:85:1C:F8:81:E1:71:07:62:F8:2E:
ED:1C:CB:5E:95:A6:34
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:www.fmovies.se
DNS:fmovies.se
Technical

DNS Lookup

A Records

Host IP Address Class TTL
fmovies.se. 104.247.81.74 IN 599

NS Records

Host Nameserver Class TTL
fmovies.se. ns1.parkingcrew.net. IN 3599
fmovies.se. ns2.parkingcrew.net. IN 3599

MX Records

Priority Host Server Class TTL
5 fmovies.se. mail.h-email.net. IN 3599

SOA Records

Domain Name Primary NS Responsible Email TTL
fmovies.se. ns1.parkingcrew.net. hostmaster.fmovies.se. 10799

TXT Records

Host Value Class TTL
fmovies.se. v=spf1 IN 3599

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Server: nginx
Date: 6th June, 2021
Content-Type: text/html; charset=UTF-8
Connection: keep-alive
Vary: Accept-Encoding

Whois Lookup

Created: 10th November, 2018
Changed: 28th February, 2021
Expires: 10th November, 2023
Registrar: 1 Api GmbH
Status: ok
Nameservers: ns1.parkingcrew.net
ns2.parkingcrew.net
Full Whois: # Copyright (c) 1997- The Swedish Internet Foundation.
# All rights reserved.
# The information obtained through searches, or otherwise, is protected
# by the Swedish Copyright Act (1960:729) and international conventions.
# It is also subject to database protection according to the Swedish
# Copyright Act.
# Any use of this material to target advertising or
# similar activities is forbidden and will be prosecuted.
# If any of the information below is transferred to a third
# party, it must be done in its entirety. This server must
# not be used as a backend for a search engine.
# Result of search for registered domain names under
# the .se top level domain.
# This whois printout is printed with UTF-8 encoding.
#
state: active
domain: fmovies.se
holder: (not shown)
admin-c: -
tech-c: -
billing-c: -
created: 2018-11-10
modified: 2021-02-28
expires: 2023-11-10
transferred: 2019-04-03
nserver: ns1.parkingcrew.net
nserver: ns2.parkingcrew.net
dnssec: unsigned delegation
registry-lock: unlocked
status: ok
registrar: 1 Api GmbH

Nameservers

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

Subdomains

Domain Subdomain
www1
www3
www4
www7
www8

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

Domain Valuation Snoop Score
$154 USD 1/5
$628 USD 1/5
0/5
$665 USD