subscene.com

subscene.com is SSL secured

Free website and domain report on subscene.com

Last Updated: 1st September, 2023 Update Now
Overview

Snoop Summary for subscene.com

This is a free and comprehensive report about subscene.com. The domain subscene.com is currently hosted on a server located in United States with the IP address 104.21.235.116, where the local currency is USD and English is the local language. Our records indicate that subscene.com is privately registered by Privacy service provided by Withheld for Privacy ehf. Subscene.com is expected to earn an estimated $20,186 USD per day from advertising revenue. The sale of subscene.com would possibly be worth $14,736,112 USD. This figure is based on the daily revenue potential of the website over a 24 month period. Subscene.com is unbelievably popular with an estimated 2,168,051 daily unique visitors. This report was last updated 1st September, 2023.

About subscene.com

Site Preview: subscene.com subscene.com
Title: Just a moment...
Description: Passionate about good subtitles this community-driven site aims to disperse and produce quality subtitles for media content including Films, TV-Series, Music Videos, and Online Video.
Keywords and Tags: popular, potential illegal software, sub scene, subscane, subscen, subscene, subscene com, subscene subtitle
Related Terms: addic7ed subtitles, avengers endgame subtitles, captain marvel subtitles, disperse, greek subtitles, open subtitles, sinhala subtitles, spanish subtitles, tv subtitles
Fav Icon:
Age: Over 22 years old
Domain Created: 24th November, 2001
Domain Updated: 8th June, 2021
Domain Expires: 24th November, 2023
Review

Snoop Score

5/5 (Perfect!)

Valuation

$14,736,112 USD
Note: All valuation figures are estimates.

Popularity

Worldwide Sensation
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 1,160
Alexa Reach:
SEMrush Rank (US): 61,016
SEMrush Authority Score: 77
Moz Domain Authority: 82
Moz Page Authority: 65

Organic vs Paid (Google Ads)

Organic Paid
Keywords: 34,921 0
Traffic: 33,204 0
Cost: $19 USD $0 USD
Traffic

Visitors

Daily Visitors: 2,168,051
Monthly Visitors: 65,988,643
Yearly Visitors: 791,338,615
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $20,186 USD
Monthly Revenue: $614,412 USD
Yearly Revenue: $7,368,051 USD
Note: All revenue figures are estimates.

Revenue By Country

SEO

Backlinks Analysis (SEMrush)

Backlinks: 50,594,781
Referring Domains: 16,145
Referring IPs: 12,093
Subscene.com has 50,594,781 backlinks according to SEMrush. 84% of these backlinks are "dofollow" (follow) links which allow the flow of link equity to pass through, which may improve subscene.com's search engine rankings. Other links are treated as 'hints' by search engines and may also pass link equity, depending on what search engines decide in each case.
100% of subscene.com's backlinks are text and image links, which are ideal for SEO. Other backlink types may be unrecognized or ignored by search engines.

Top New Follow Links

1
Source: https://dramakoreaindo.com/drama-korea-romantic-doctor-teacher-kim-subtitle-indonesia/
Target: https://subscene.com/subtitles/romantic-doctor-teacher-kim-2016-2

2
Source: https://dramakoreaindo.com/drama-korea-romantic-doctor-teacher-kim-subtitle-indonesia/
Target: https://subscene.com/subtitles/romantic-doctor-teacher-kim-2016-2

3
Source: https://banglasubtitle.com/movies/spider-man-far-from-home-bangla-subtitle/
Target: https://subscene.com/subtitles/spider-man-far-from-home/bengali/2055139

4
Source: https://banglasubtitle.com/movies/spider-man-far-from-home-bangla-subtitle/
Target: https://subscene.com/subtitles/spider-man-far-from-home/bengali/2054825

5
Source: https://asiautaf.com/page/473/
Target: https://subscene.com/subtitles/jimi-ni-sugoi-koetsu-girl

Top Ranking Keywords (US)

1
Keyword: subscene
Ranked Page: https://subscene.com/browse/popular/all/1

2
Keyword: subscene com
Ranked Page: https://subscene.com/browse/popular/all/1

3
Keyword: subscane
Ranked Page: https://subscene.com/browse/popular/all/1

4
Keyword: subscene subtitle
Ranked Page: https://subscene.com/browse/popular/all/1

5
Keyword: sub scene
Ranked Page: https://subscene.com/browse/popular/all/1

Domain Analysis

Value Length
Domain: subscene.com 12
Domain Name: subscene 8
Extension (TLD): com 3
Expiry Check:

Page Speed Analysis

Average Load Time: 1.03 seconds
Load Time Comparison: Faster than 70% of sites

PageSpeed Insights

Avg. (All Categories) 74
Performance 99
Accessibility 65
Best Practices 92
SEO 92
PWA 22
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://subscene.com/
Updated: 10th January, 2022

1.42 seconds
First Contentful Paint (FCP)
83%
9%
8%

0.00 seconds
First Input Delay (FID)
97%
1%
2%

Simulate loading on desktop
99

Performance

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

Metrics

First Contentful Paint — 0.4 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 0.7 s
The time taken for the page to become fully interactive.
Speed Index — 0.8 s
The time taken for the page contents to be visibly populated.
Total Blocking Time — 10 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Largest Contentful Paint — 0.9 s
The timing of the largest text or image that is painted.
Cumulative Layout Shift — 0.062
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

Max Potential First Input Delay — 60 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 0.4 s
The time taken for the primary content of the page to be rendered.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://subscene.com/
http/1.1
0
53.300000028685
684
0
301
text/plain
https://subscene.com/
h2
53.638999990653
592.0599999954
5765
20829
200
text/html
Document
https://subscene.com/css?v=7gFkAkX5jD-dB0pnKagqvh3pZA2Yls80efqHXQ_7IIc1
h2
612.15000000084
1014.1239999793
11850
38996
200
text/css
Stylesheet
https://subscene.com/js?v=gGSGH6YeGLyiuBi8eaD9RxXpnLe9W0Fp1mILQxc5EYw1
h2
612.32000001473
882.21800001338
1192
892
200
text/javascript
Script
https://subscene.com/cdn-cgi/bm/cv/669835187/api.js
h2
1019.4299999857
1039.4240000169
9855
35662
200
text/javascript
Script
https://i.jeded.com/i/sing-2.135-225628.jpg
h2
1019.5889999741
1084.7400000202
12466
11574
200
image/jpeg
Image
https://i.jeded.com/i/pushpa-the-rise-part-1.135-227630.jpg
h2
1019.718000025
1085.1460000267
12090
11205
200
image/jpeg
Image
https://i.jeded.com/i/the-355.135-196145.jpg
h2
1020.4340000055
1084.2490000068
13527
12643
200
image/jpeg
Image
https://i.jeded.com/i/shingeki-no-kyojin-the-final-season-part-2-attack-on-titan-the-final-season-part-2.135-229851.jpg
h2
1020.6260000123
1087.4140000087
15984
15093
200
image/jpeg
Image
https://i.jeded.com/i/running-man-2010-7.135-157565.jpg
h2
1020.7860000082
1085.5100000044
14767
13880
200
image/jpeg
Image
https://ads.jeded.com/user.js
h2
884.10299998941
1041.2660000147
1040
79
200
application/x-javascript
Script
https://ads.jeded.com/ads/1.js
h2
1015.8240000019
1198.5320000094
9536
25947
200
application/x-javascript
Script
https://subscene.com/content/images/clouds.gif
h2
1023.1139999814
1096.6379999882
3172
2412
200
image/gif
Image
https://subscene.com/content/images/mountains.gif
h2
1023.320999986
1047.4570000079
6337
5588
200
image/gif
Image
data
1022.9689999833
1023.1500000227
0
1397
200
image/png
Image
data
1023.6879999866
1023.8099999842
0
935
200
image/png
Image
https://subscene.com/content/images/logo.gif
h2
1025.0150000211
1078.6380000063
5019
4265
200
image/gif
Image
https://subscene.com/content/images/icon-rating-positive.png
h2
1052.7020000154
1121.0500000161
1738
988
200
image/png
Image
https://subscene.com/content/images/icon-rating-neutral.png
h2
1053.2399999793
1080.3719999967
1819
1056
200
image/png
Image
https://www.google-analytics.com/analytics.js
h2
1110.2659999742
1114.6859999862
20631
50205
200
text/javascript
Script
data
1112.358000013
1112.5239999965
0
1707
200
image/png
Image
https://www.google-analytics.com/j/collect?v=1&_v=j96&a=1666773352&t=pageview&_s=1&dl=https%3A%2F%2Fsubscene.com%2F&ul=en-us&de=UTF-8&dt=Subscene%20-%20Passionate%20about%20good%20subtitles&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=IEBAAAABAAAAAC~&jid=243787524&gjid=901230512&cid=921227019.1641795985&tid=UA-340707-2&_gid=1637575625.1641795985&_r=1&_slc=1&z=70013657
h2
1157.4460000265
1161.7689999985
613
4
200
text/plain
XHR
https://stats.g.doubleclick.net/j/collect?t=dc&aip=1&_r=3&v=1&_v=j96&tid=UA-340707-2&cid=921227019.1641795985&jid=243787524&gjid=901230512&_gid=1637575625.1641795985&_u=IEBAAAAAAAAAAC~&z=439093826
h2
1164.654000022
1168.9200000255
683
1
200
text/plain
XHR
https://subscene.com/cdn-cgi/bm/cv/result?req_id=6cb3d564ba195d85
h2
1350.3260000143
1377.1210000268
860
0
204
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)
639.708
10.2
1060.131
22.542
1082.69
5.419
1093.282
45.425
1154.036
10.314
1173.609
26.737
1243.875
8.884
1266.198
57.795
1328.803
56.138
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Other

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Subscene.com 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. Subscene.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Subscene.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Subscene.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Subscene.com should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Subscene.com 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.
Initial server response time was short — Root document took 540 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)
https://subscene.com/
539.415
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Subscene.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://subscene.com/
190
https://subscene.com/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Subscene.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers — Potential savings of 0 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
https://ads.jeded.com/ads/1.js
74
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
Avoids enormous network payloads — Total size was 146 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.google-analytics.com/analytics.js
20631
https://i.jeded.com/i/shingeki-no-kyojin-the-final-season-part-2-attack-on-titan-the-final-season-part-2.135-229851.jpg
15984
https://i.jeded.com/i/running-man-2010-7.135-157565.jpg
14767
https://i.jeded.com/i/the-355.135-196145.jpg
13527
https://i.jeded.com/i/sing-2.135-225628.jpg
12466
https://i.jeded.com/i/pushpa-the-rise-part-1.135-227630.jpg
12090
https://subscene.com/css?v=7gFkAkX5jD-dB0pnKagqvh3pZA2Yls80efqHXQ_7IIc1
11850
https://subscene.com/cdn-cgi/bm/cv/669835187/api.js
9855
https://ads.jeded.com/ads/1.js
9536
https://subscene.com/content/images/mountains.gif
6337
Avoids an excessive DOM size — 316 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
316
Maximum DOM Depth
13
Maximum Child Elements
12
Avoid chaining critical requests — 4 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Subscene.com should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.1 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://subscene.com/
119.325
12.835
3.02
https://subscene.com/cdn-cgi/bm/cv/669835187/api.js
118.875
116.901
0.729
Minimizes main-thread work — 0.3 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
164.615
Style & Layout
59.348
Other
42.166
Rendering
25.345
Parse HTML & CSS
8.824
Script Parsing & Compilation
5.789
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 — 21 requests • 146 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
21
149628
Image
10
86919
Script
5
42254
Stylesheet
1
11850
Document
1
5765
Other
4
2840
Media
0
0
Font
0
0
Third-party
10
101337
Minimize third-party usage — Third-party code blocked the main thread for 0 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
21244
0
683
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Element
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 — 2 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://subscene.com/cdn-cgi/bm/cv/669835187/api.js
610
58
https://subscene.com/cdn-cgi/bm/cv/669835187/api.js
668
56
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
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 subscene.com on mobile screens.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Other

Serve static assets with an efficient cache policy — 12 resources found
Subscene.com 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://subscene.com/content/images/mountains.gif
1800000
6337
https://subscene.com/content/images/logo.gif
1800000
5019
https://subscene.com/content/images/clouds.gif
1800000
3172
https://subscene.com/content/images/icon-rating-neutral.png
1800000
1819
https://subscene.com/content/images/icon-rating-positive.png
1800000
1738
https://www.google-analytics.com/analytics.js
7200000
20631
https://i.jeded.com/i/shingeki-no-kyojin-the-final-season-part-2-attack-on-titan-the-final-season-part-2.135-229851.jpg
14400000
15984
https://i.jeded.com/i/running-man-2010-7.135-157565.jpg
14400000
14767
https://i.jeded.com/i/the-355.135-196145.jpg
14400000
13527
https://i.jeded.com/i/sing-2.135-225628.jpg
14400000
12466
https://i.jeded.com/i/pushpa-the-rise-part-1.135-227630.jpg
14400000
12090
https://subscene.com/cdn-cgi/bm/cv/669835187/api.js
604800000
9855

Other

Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL
https://i.jeded.com/i/the-355.135-196145.jpg
https://i.jeded.com/i/shingeki-no-kyojin-the-final-season-part-2-attack-on-titan-the-final-season-part-2.135-229851.jpg
https://i.jeded.com/i/sing-2.135-225628.jpg
https://i.jeded.com/i/pushpa-the-rise-part-1.135-227630.jpg
https://i.jeded.com/i/running-man-2010-7.135-157565.jpg
65

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of subscene.com. 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.
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.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

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

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

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

Contrast

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

Navigation

Heading elements are not 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.
Failing Elements

Names and labels

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
Form elements do not have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Failing Elements
Links do not have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.

Manual Checks

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

Best Practices

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

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

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

Audits

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

Audits

Does not use HTTPS — 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 Request Resolution
http://subscene.com/
Allowed
92

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for subscene.com. 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 subscene.com on mobile screens.
Document uses legible font sizes
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Tap targets are sized appropriately
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

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

Crawling and Indexing

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

Content Best Practices

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

Manual Checks

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

PWA

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of subscene.com. 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 subscene.com on mobile screens.

Installable

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

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Does not provide a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

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

1.86 seconds
First Contentful Paint (FCP)
75%
15%
10%

0.11 seconds
First Input Delay (FID)
75%
23%
2%

Simulate loading on mobile
88

Performance

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

Metrics

First Contentful Paint — 1.3 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 2.9 s
The time taken for the page to become fully interactive.
Speed Index — 1.9 s
The time taken for the page contents to be visibly populated.
Cumulative Layout Shift — 0.057
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Audits

First Meaningful Paint — 1.3 s
The time taken for the primary content of the page to be rendered.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://subscene.com/
http/1.1
0
37.815999996383
659
0
301
text/plain
https://subscene.com/
h2
38.125999999465
407.7770000149
5760
20829
200
text/html
Document
https://subscene.com/css?v=7gFkAkX5jD-dB0pnKagqvh3pZA2Yls80efqHXQ_7IIc1
h2
419.98599999351
829.19000001857
11842
38996
200
text/css
Stylesheet
https://subscene.com/js?v=gGSGH6YeGLyiuBi8eaD9RxXpnLe9W0Fp1mILQxc5EYw1
h2
420.37500001607
680.50000001676
1190
892
200
text/javascript
Script
https://subscene.com/cdn-cgi/bm/cv/669835187/api.js
h2
834.29699999397
857.62500000419
9861
35662
200
text/javascript
Script
https://i.jeded.com/i/sing-2.135-225628.jpg
h2
834.50200001244
867.73399999947
12468
11574
200
image/jpeg
Image
https://i.jeded.com/i/pushpa-the-rise-part-1.135-227630.jpg
h2
834.65599999181
887.81099999323
12088
11205
200
image/jpeg
Image
https://i.jeded.com/i/the-355.135-196145.jpg
h2
835.02100000624
900.11899999809
13531
12643
200
image/jpeg
Image
https://i.jeded.com/i/shingeki-no-kyojin-the-final-season-part-2-attack-on-titan-the-final-season-part-2.135-229851.jpg
h2
835.26600000914
886.0590000113
15986
15093
200
image/jpeg
Image
https://i.jeded.com/i/running-man-2010-7.135-157565.jpg
h2
835.41500000865
871.4869999967
14779
13880
200
image/jpeg
Image
https://ads.jeded.com/user.js
h2
682.09300001035
831.1120000144
1038
79
200
application/x-javascript
Script
https://ads.jeded.com/ads/1.js
h2
830.81899999524
983.59000001801
9534
25947
200
application/x-javascript
Script
https://subscene.com/content/images/clouds.gif
h2
837.78600001824
868.94000001485
3163
2412
200
image/gif
Image
https://subscene.com/content/images/mountains.gif
h2
837.95800001826
862.1620000049
6341
5588
200
image/gif
Image
data
837.74899999844
837.91800000472
0
1397
200
image/png
Image
data
838.37800001493
838.51500001037
0
935
200
image/png
Image
https://subscene.com/content/images/logo.gif
h2
839.69799999613
863.52899999474
5020
4265
200
image/gif
Image
https://subscene.com/content/images/icon-rating-positive.png
h2
860.16100001871
887.03499999247
1738
988
200
image/png
Image
https://subscene.com/content/images/icon-rating-neutral.png
h2
860.87900001439
885.66699999501
1807
1056
200
image/png
Image
data
880.94600001932
881.06899999548
0
1707
200
image/png
Image
https://www.google-analytics.com/analytics.js
h2
920.40200001793
926.34700000053
20631
50205
200
text/javascript
Script
https://www.google-analytics.com/j/collect?v=1&_v=j96&a=1228426655&t=pageview&_s=1&dl=https%3A%2F%2Fsubscene.com%2F&ul=en-us&de=UTF-8&dt=Subscene%20-%20Passionate%20about%20good%20subtitles&sd=24-bit&sr=360x640&vp=360x640&je=0&_u=IEBAAAABAAAAAC~&jid=1992174705&gjid=1204308464&cid=88795104.1641795999&tid=UA-340707-2&_gid=59441894.1641795999&_r=1&_slc=1&z=302852482
h2
975.88400001405
979.94399999152
613
4
200
text/plain
XHR
https://stats.g.doubleclick.net/j/collect?t=dc&aip=1&_r=3&v=1&_v=j96&tid=UA-340707-2&cid=88795104.1641795999&jid=1992174705&gjid=1204308464&_gid=59441894.1641795999&_u=IEBAAAAAAAAAAC~&z=1718836397
h2
982.3960000067
985.87500001304
683
1
200
text/plain
XHR
https://subscene.com/cdn-cgi/bm/cv/result?req_id=6cb3d5bef8b45967
h2
1098.4490000119
1116.7350000178
856
0
204
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)
447.688
7.428
869.933
12.892
882.84
10.069
895.702
11.645
915.477
34.651
950.242
5.06
964.266
18.396
989.269
23.739
1022.928
7.194
1044.245
47.73
1096.805
38.217
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data
Script Treemap Data
Provide as required, for treemap app.

Other

Properly size images
Images can slow down the page's load time. Subscene.com should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Subscene.com should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Subscene.com should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Subscene.com should consider minifying JS files.
Reduce unused CSS
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Subscene.com 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.
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)
https://subscene.com/
370.639
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Subscene.com should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://subscene.com/
630
https://subscene.com/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Subscene.com should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers — Potential savings of 0 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
https://ads.jeded.com/ads/1.js
74
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.
Avoids enormous network payloads — Total size was 146 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://www.google-analytics.com/analytics.js
20631
https://i.jeded.com/i/shingeki-no-kyojin-the-final-season-part-2-attack-on-titan-the-final-season-part-2.135-229851.jpg
15986
https://i.jeded.com/i/running-man-2010-7.135-157565.jpg
14779
https://i.jeded.com/i/the-355.135-196145.jpg
13531
https://i.jeded.com/i/sing-2.135-225628.jpg
12468
https://i.jeded.com/i/pushpa-the-rise-part-1.135-227630.jpg
12088
https://subscene.com/css?v=7gFkAkX5jD-dB0pnKagqvh3pZA2Yls80efqHXQ_7IIc1
11842
https://subscene.com/cdn-cgi/bm/cv/669835187/api.js
9861
https://ads.jeded.com/ads/1.js
9534
https://subscene.com/content/images/mountains.gif
6341
Avoids an excessive DOM size — 316 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
316
Maximum DOM Depth
13
Maximum Child Elements
12
Avoid chaining critical requests — 4 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Subscene.com 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://subscene.com/
459.352
25.84
18.776
https://subscene.com/cdn-cgi/bm/cv/669835187/api.js
366.872
355.672
6.984
Unattributable
110.416
12.792
0.856
https://www.google-analytics.com/analytics.js
107.232
94.504
3.712
Minimizes main-thread work — 1.1 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
507.584
Style & Layout
198.072
Other
177.064
Rendering
132.8
Script Parsing & Compilation
33.032
Parse HTML & CSS
31.824
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 — 21 requests • 146 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
21
149588
Image
10
86921
Script
5
42254
Stylesheet
1
11842
Document
1
5760
Other
4
2811
Media
0
0
Font
0
0
Third-party
10
101351
Minimize third-party usage — Third-party code blocked the main thread for 40 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)
21244
37.68
683
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Element
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://subscene.com/cdn-cgi/bm/cv/669835187/api.js
2190
191
https://subscene.com/cdn-cgi/bm/cv/669835187/api.js
2381
153
https://www.google-analytics.com/analytics.js
2820
95
https://subscene.com/
1153
69
Avoid non-composited animations
It is recommended to avoid non-composited animations which are often janky and increase CLS.
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 subscene.com on mobile screens.
First Contentful Paint (3G) — 2486 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.

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

Total Blocking Time — 290 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).
Largest Contentful Paint — 2.9 s
The timing of the largest text or image that is painted.

Audits

Max Potential First Input Delay — 190 ms
Users could experience a delay when interacting with the page.

Other

Eliminate render-blocking resources — Potential savings of 160 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Subscene.com 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://subscene.com/css?v=7gFkAkX5jD-dB0pnKagqvh3pZA2Yls80efqHXQ_7IIc1
11842
150
Serve static assets with an efficient cache policy — 12 resources found
Subscene.com 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://subscene.com/content/images/mountains.gif
1800000
6341
https://subscene.com/content/images/logo.gif
1800000
5020
https://subscene.com/content/images/clouds.gif
1800000
3163
https://subscene.com/content/images/icon-rating-neutral.png
1800000
1807
https://subscene.com/content/images/icon-rating-positive.png
1800000
1738
https://www.google-analytics.com/analytics.js
7200000
20631
https://i.jeded.com/i/shingeki-no-kyojin-the-final-season-part-2-attack-on-titan-the-final-season-part-2.135-229851.jpg
14400000
15986
https://i.jeded.com/i/running-man-2010-7.135-157565.jpg
14400000
14779
https://i.jeded.com/i/the-355.135-196145.jpg
14400000
13531
https://i.jeded.com/i/sing-2.135-225628.jpg
14400000
12468
https://i.jeded.com/i/pushpa-the-rise-part-1.135-227630.jpg
14400000
12088
https://subscene.com/cdn-cgi/bm/cv/669835187/api.js
604800000
9861

Other

Image elements do not have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.
URL
https://i.jeded.com/i/the-355.135-196145.jpg
https://i.jeded.com/i/shingeki-no-kyojin-the-final-season-part-2-attack-on-titan-the-final-season-part-2.135-229851.jpg
https://i.jeded.com/i/sing-2.135-225628.jpg
https://i.jeded.com/i/pushpa-the-rise-part-1.135-227630.jpg
https://i.jeded.com/i/running-man-2010-7.135-157565.jpg
65

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of subscene.com. 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.
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.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

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

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

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

Contrast

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

Navigation

Heading elements are not 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.
Failing Elements

Names and labels

Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Failing Elements
Form elements do not have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Failing Elements
Links do not have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.

Manual Checks

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

Best Practices

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

Audits

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.
Ensure CSP is effective against XSS attacks
Significantly reduce the risk of cross-site scripting attacks (XSS) by ensuring you have a strong Content Security Policy (CSP).
Description Directive Severity
No CSP found in enforcement mode
High

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

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

Audits

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

Audits

Does not use HTTPS — 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 Request Resolution
http://subscene.com/
Allowed

Audits

Serves images with low resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
URL Displayed size Actual size Expected size
https://i.jeded.com/i/the-355.135-196145.jpg
135 x 214
135 x 214
270 x 428
https://i.jeded.com/i/shingeki-no-kyojin-the-final-season-part-2-attack-on-titan-the-final-season-part-2.135-229851.jpg
135 x 204
135 x 204
270 x 408
https://i.jeded.com/i/pushpa-the-rise-part-1.135-227630.jpg
135 x 202
135 x 202
270 x 404
https://i.jeded.com/i/running-man-2010-7.135-157565.jpg
135 x 202
135 x 202
270 x 404
https://i.jeded.com/i/sing-2.135-225628.jpg
135 x 202
135 x 202
270 x 404
88

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for subscene.com. 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 subscene.com on mobile screens.
Document uses legible font sizes — 98.83% 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
a
0.64%
10px
html, body, div, span, object, iframe, h1, h2, h3, h4, h5, h6, p, blockquote, pre, abbr, address, cite, code, del, dfn, em, img, ins, kbd, q, samp, small, strong, var, b, i, dl, dt, dd, ol, ul, li, fieldset, form, label, legend, table, caption, tbody, tfoot, thead, tr, th, td, article, aside, canvas, details, figcaption, figure, footer, header, hgroup, menu, nav, section, summary, time, mark, audio, video
0.52%
10px
98.83%
≥ 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.
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.
Page isn’t blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Content Best Practices

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

Mobile Friendly

Tap targets are not sized appropriately — 39% 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
23x11
23x11
170x15
211x15
205x15
195x15
186x15
23x11
145x15
91x15
145x15
91x15
193x15
80x15
237x15
53x15
53x15
271x15
242x15
80x15
212x15
67x15
164x15
164x15
91x15
91x15
200x15
64x15
64x15
223x15
205x15
195x15
159x15
23x11
23x11
23x11
23x11
72x15
48x17
59x17
145x15
250x15
103x15
121x14

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

PWA

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

PWA Optimized

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 subscene.com on mobile screens.

Installable

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

PWA Optimized

Does not register a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Is not configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Does not set a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Content is not 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.
Does not provide a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.
Manifest doesn't have a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

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

Server Location

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

Web Hosting Provider

Name IP Address
Cloudflare, Inc.
Registration

Domain Registrant

Private Registration: Yes
Name: Redacted for Privacy
Organization: Privacy service provided by Withheld for Privacy ehf
Country: IS
City: Reykjavik
State: Capital Region
Post Code: 101
Email: 4b42588c9a0e4f64a055c942cf35e202.protect@withheldforprivacy.com
Phone: +354.4212434
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
NAMECHEAP INC 104.16.100.56
Security

Visitor Safety

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

SSL/TLS Certificate

Issued To: sni.cloudflaressl.com
Issued By: Cloudflare Inc ECC CA-3
Valid From: 12th March, 2023
Valid To: 10th March, 2024
Subject: CN = sni.cloudflaressl.com
O = Cloudflare, Inc.
L = San Francisco
S = US
Hash: c959965e
Issuer: CN = Cloudflare Inc ECC CA-3
O = Cloudflare, Inc.
S = US
Version: 2
Serial Number: 13373311455044146055826858106791343410
Serial Number (Hex): 0A0F9B29489DD6ABEB82D890E8AF3532
Valid From: 12th March, 2024
Valid To: 10th March, 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.23.140.1.2.2
CPS: http://www.digicert.com/CPS

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 : EE:CD:D0:64:D5:DB:1A:CE:C5:5C:B7:9D:B4:CD:13:A2:
32:87:46:7C:BC:EC:DE:C3:51:48:59:46:71:1F:B5:9B
Timestamp : Mar 12 07:45:52.733 2023 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:67:9F:E3:0D:9E:1B:DC:33:F9:DB:AD:9B:
59:F2:2D:BA:0E:36:43:AE:09:BB:6F:0C:BB:49:E4:B0:
51:76:C8:B5:02:20:40:90:48:C8:1D:CB:19:4A:92:0A:
EA:F3:30:9C:AB:9B:6F:0C:56:C7:6A:86:84:D5:77:E4:
02:E0:F5:44:36:19
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 73:D9:9E:89:1B:4C:96:78:A0:20:7D:47:9D:E6:B2:C6:
1C:D0:51:5E:71:19:2A:8C:6B:80:10:7A:C1:77:72:B5
Timestamp : Mar 12 07:45:52.843 2023 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:BD:C9:C7:99:AC:72:15:EC:C0:D4:B5:
60:3F:79:79:87:E8:46:4E:D0:00:EA:4D:12:C1:3D:31:
22:E6:18:E0:49:02:21:00:D3:F4:4C:11:B5:38:2A:61:
64:35:96:28:DC:26:F1:14:8D:05:6F:E5:0E:C1:48:B3:
27:2B:E6:F3:FF:AA:58:FE
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 48:B0:E3:6B:DA:A6:47:34:0F:E5:6A:02:FA:9D:30:EB:
1C:52:01:CB:56:DD:2C:81:D9:BB:BF:AB:39:D8:84:73
Timestamp : Mar 12 07:45:52.783 2023 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:B6:0C:68:41:43:07:9E:30:B4:51:CE:
01:3A:68:B0:A7:D7:89:87:32:49:99:0F:11:3F:A5:07:
39:3E:FC:C2:8F:02:20:2E:1D:EA:46:D4:47:EC:FA:4D:
70:C7:78:CD:36:8D:39:2D:BF:F8:FD:11:F9:A1:6A:3D:
89:94:34:63:F8:67:A8
Key Usage: Digital Signature
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:*.subscene.com
DNS:subscene.com
DNS:sni.cloudflaressl.com
Technical

DNS Lookup

HTTP Response Headers

HTTP-Code: HTTP/1.1 403 Forbidden
Date: 15th March, 2023
Content-Type: text/html; charset=UTF-8
Cache-Control: private, max-age=0, no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Expires: 1st January, 1970
Server: cloudflare
Connection: close
Cross-Origin-Embedder-Policy: require-corp
Cross-Origin-Opener-Policy: same-origin
Cross-Origin-Resource-Policy: same-origin
Permissions-Policy: accelerometer=(),autoplay=(),camera=(),clipboard-read=(),clipboard-write=(),fullscreen=(),geolocation=(),gyroscope=(),hid=(),interest-cohort=(),magnetometer=(),microphone=(),payment=(),publickey-credentials-get=(),screen-wake-lock=(),serial=(),sync-xhr=(),usb=()
Referrer-Policy: same-origin
X-Frame-Options: SAMEORIGIN
Report-To: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3?s=xcfFmI15%2FAbk0eTCHdajHOEHgy3xnbpMVFITmH7p0p5n7Thhd2jarDsv7bGCaxZqVK5DdWutyE%2BsBZudC0dYKJLtfY1Fy7mqcD5eP%2FG2mzp4JvZ5NDqVSzYhmwOHMqo%3D"}],"group":"cf-nel","max_age":604800}
NEL: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
CF-RAY: 7a817aec5ff343a4-EWR
alt-svc: h3=":443"; ma=86400, h3-29=":443"; ma=86400

Whois Lookup

Created: 24th November, 2001
Changed: 8th June, 2021
Expires: 24th November, 2023
Registrar: NAMECHEAP INC
Status: clientTransferProhibited
transferPeriod
Nameservers: gail.ns.cloudflare.com
kip.ns.cloudflare.com
Owner Name: Redacted for Privacy
Owner Organization: Privacy service provided by Withheld for Privacy ehf
Owner Street: Kalkofnsvegur 2
Owner Post Code: 101
Owner City: Reykjavik
Owner State: Capital Region
Owner Country: IS
Owner Phone: +354.4212434
Owner Email: 4b42588c9a0e4f64a055c942cf35e202.protect@withheldforprivacy.com
Admin Name: Redacted for Privacy
Admin Organization: Privacy service provided by Withheld for Privacy ehf
Admin Street: Kalkofnsvegur 2
Admin Post Code: 101
Admin City: Reykjavik
Admin State: Capital Region
Admin Country: IS
Admin Phone: +354.4212434
Admin Email: 4b42588c9a0e4f64a055c942cf35e202.protect@withheldforprivacy.com
Tech Name: Redacted for Privacy
Tech Organization: Privacy service provided by Withheld for Privacy ehf
Tech Street: Kalkofnsvegur 2
Tech Post Code: 101
Tech City: Reykjavik
Tech State: Capital Region
Tech Country: IS
Tech Phone: +354.4212434
Tech Email: 4b42588c9a0e4f64a055c942cf35e202.protect@withheldforprivacy.com
Full Whois: Domain name: subscene.com
Registry Domain ID: 80199699_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.namecheap.com
Registrar URL: http://www.namecheap.com
Updated Date: 2021-06-08T16:51:10.00Z
Creation Date: 2001-11-24T10:55:29.00Z
Registrar Registration Expiration Date: 2023-11-24T10:55:29.00Z
Registrar: NAMECHEAP INC
Registrar IANA ID: 1068
Registrar Abuse Contact Email: abuse@namecheap.com
Registrar Abuse Contact Phone: +1.9854014545
Reseller: NAMECHEAP INC
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: transferPeriod https://icann.org/epp#transferPeriod
Registry Registrant ID:
Registrant Name: Redacted for Privacy
Registrant Organization: Privacy service provided by Withheld for Privacy ehf
Registrant Street: Kalkofnsvegur 2
Registrant City: Reykjavik
Registrant State/Province: Capital Region
Registrant Postal Code: 101
Registrant Country: IS
Registrant Phone: +354.4212434
Registrant Phone Ext:
Registrant Fax:
Registrant Fax Ext:
Registrant Email: 4b42588c9a0e4f64a055c942cf35e202.protect@withheldforprivacy.com
Registry Admin ID:
Admin Name: Redacted for Privacy
Admin Organization: Privacy service provided by Withheld for Privacy ehf
Admin Street: Kalkofnsvegur 2
Admin City: Reykjavik
Admin State/Province: Capital Region
Admin Postal Code: 101
Admin Country: IS
Admin Phone: +354.4212434
Admin Phone Ext:
Admin Fax:
Admin Fax Ext:
Admin Email: 4b42588c9a0e4f64a055c942cf35e202.protect@withheldforprivacy.com
Registry Tech ID:
Tech Name: Redacted for Privacy
Tech Organization: Privacy service provided by Withheld for Privacy ehf
Tech Street: Kalkofnsvegur 2
Tech City: Reykjavik
Tech State/Province: Capital Region
Tech Postal Code: 101
Tech Country: IS
Tech Phone: +354.4212434
Tech Phone Ext:
Tech Fax:
Tech Fax Ext:
Tech Email: 4b42588c9a0e4f64a055c942cf35e202.protect@withheldforprivacy.com
Name Server: kip.ns.cloudflare.com
Name Server: gail.ns.cloudflare.com
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2023-03-14T20:55:58.16Z <<<
For more information on Whois status codes, please visit https://icann.org/epp

Nameservers

Name IP Address
gail.ns.cloudflare.com 173.245.58.116
kip.ns.cloudflare.com 172.64.33.128
Related

Subdomains

Domain Subdomain
u

Similar Sites

Domain Valuation Snoop Score
$3,630 USD 3/5
$1,627 USD 2/5
$266 USD 2/5
0/5
$14,174 USD 3/5

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
$1,002 USD
$705 USD
0/5
0/5

Sites hosted on the same IP address