burningseries.to

burningseries.to is SSL secured

Free website and domain report on burningseries.to

Last Updated: 25th July, 2023 Update Now
Overview

Snoop Summary for burningseries.to

This is a free and comprehensive report about burningseries.to. The domain burningseries.to is currently hosted on a server located in United States with the IP address 172.67.205.115, where USD is the local currency and the local language is English. Burningseries.to has the potential to be earning an estimated $1 USD per day from advertising revenue. If burningseries.to was to be sold it would possibly be worth $971 USD (based on the daily revenue potential of the website over a 24 month period). Burningseries.to receives an estimated 462 unique visitors every day - a decent amount of traffic! This report was last updated 25th July, 2023.

About burningseries.to

Site Preview: burningseries.to burningseries.to
Title: Burningseries.to - Serien online sehen auf Burning Series
Description: Schaue auf Burning Series mehr als 4000 Serien wie Die Simpsons, The Big Bang Theory und viele mehr gratis.
Keywords and Tags: parked domain
Related Terms: burning board, burning seri.es, burning series anime, burning series app, burning series down, burning series serien, flume burning man, serien load, stomach burning
Fav Icon:
Age:
Domain Created:
Domain Updated:
Domain Expires:
Review

Snoop Score

1/5

Valuation

$971 USD
Note: All valuation figures are estimates.

Popularity

Low
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 1,742,967
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: 462
Monthly Visitors: 14,062
Yearly Visitors: 168,630
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $1 USD
Monthly Revenue: $40 USD
Yearly Revenue: $481 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: burningseries.to 16
Domain Name: burningseries 13
Extension (TLD): to 2

Page Speed Analysis

Average Load Time:
Load Time Comparison:

PageSpeed Insights

Avg. (All Categories) 59
Performance 52
Accessibility 64
Best Practices 75
SEO 82
PWA 22
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://burningseries.to/
Updated: 8th March, 2022

1.21 seconds
First Contentful Paint (FCP)
88%
7%
5%

0.00 seconds
First Input Delay (FID)
100%
0%
0%

Simulate loading on desktop
52

Performance

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

Metrics

Cumulative Layout Shift — 0.021
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Burningseries.to should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Burningseries.to should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Burningseries.to should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Burningseries.to should consider minifying JS files.
Reduce unused CSS — Potential savings of 45 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Burningseries.to should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.youtube.com/s/player/2fd2ad45/www-player.css
47892
46166
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 120 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://burningseries.to/
117.377
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Burningseries.to should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://burningseries.to/
190
https://burningseries.to/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Burningseries.to 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.
URL Potential Savings (Ms)
https://burningseries.to/burningseries.png
0
Avoids enormous network payloads — Total size was 1,357 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://burningseries.to/burningseries.png
566708
https://www.youtube.com/s/player/2fd2ad45/player_ias.vflset/en_US/base.js
536853
https://www.youtube.com/s/player/2fd2ad45/www-embed-player.vflset/www-embed-player.js
89089
https://www.youtube.com/s/player/2fd2ad45/www-player.css
47892
https://www.googletagmanager.com/gtag/js?id=UA-31958500-1
37643
https://www.youtube.com/embed/bRaUrTQsyeg?start=15
25596
https://www.google-analytics.com/analytics.js
20631
https://www.google.com/js/th/b11n7QwaEucVJQMKB-LsSDNLMoQ5L9B69t4x3UT_5Ww.js
14596
https://fonts.gstatic.com/s/roboto/v18/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
11676
https://www.youtube.com/s/player/2fd2ad45/player_ias.vflset/en_US/embed.js
8544
Avoids an excessive DOM size — 80 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
80
Maximum DOM Depth
9
Maximum Child Elements
34
Avoid chaining critical requests — 6 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Burningseries.to 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 — 3 user timings
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
Name Type Start Time (Ms) Duration (Ms)
mark_pe
Mark
1918.434
mark_fs
Mark
2131.411
mark_qoes
Mark
2224.605
Keep request counts low and transfer sizes small — 27 requests • 1,357 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
27
1389124
Script
9
713277
Image
2
566932
Stylesheet
7
65271
Document
2
28710
Font
1
11676
Other
6
3258
Media
0
0
Third-party
17
799715
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
Avoid large layout shifts — 5 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.018997131818531
0.0005443135398973
0.0005443135398973
0.0005443135398973
0.00051501117967445
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 — 10 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://www.youtube.com/s/player/2fd2ad45/player_ias.vflset/en_US/base.js
1970
508
https://www.youtube.com/s/player/2fd2ad45/player_ias.vflset/en_US/base.js
3035
357
https://www.youtube.com/s/player/2fd2ad45/www-embed-player.vflset/www-embed-player.js
2478
287
https://www.youtube.com/s/player/2fd2ad45/www-player.css
861
164
https://www.googletagmanager.com/gtag/js?id=UA-31958500-1
701
160
https://www.youtube.com/s/player/2fd2ad45/www-embed-player.vflset/www-embed-player.js
1172
114
https://burningseries.to/
403
101
https://www.youtube.com/s/player/2fd2ad45/player_ias.vflset/en_US/base.js
2766
93
https://burningseries.to/
340
63
Unattributable
549
61
Avoid non-composited animations — 6 animated elements found
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Element Name
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 burningseries.to on mobile screens.
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.

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.

Audits

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://burningseries.to/
http/1.1
0
195.77300001401
738
0
301
text/plain
https://burningseries.to/
h2
196.14600000205
312.52800000948
3114
5446
200
text/html
Document
https://www.googletagmanager.com/gtag/js?id=UA-31958500-1
h2
334.34500001022
399.47699999902
37643
94543
200
application/javascript
Script
https://burningseries.to/banner-styles.css
h2
334.55600001616
593.01700000651
3126
11152
200
text/css
Stylesheet
https://burningseries.to/screen.css
h2
334.67199999723
593.96100000595
1241
1245
200
text/css
Stylesheet
https://burningseries.to/burningseries.png
h2
391.18599999347
798.04100000183
566708
565897
200
image/png
Image
https://burningseries.to/cdn-cgi/scripts/5c5dd728/cloudflare-static/email-decode.min.js
h2
335.12000000337
593.71400001692
1470
1239
200
application/javascript
Script
https://www.youtube.com/embed/bRaUrTQsyeg?start=15
h2
402.13299999596
593.4089999937
25596
58750
200
text/html
Document
https://www.google-analytics.com/analytics.js
h2
592.43300001253
608.47900001681
20631
50205
200
text/javascript
Script
https://burningseries.to/reset.css
h2
608.24699999648
798.82699999143
2806
8418
200
text/css
Stylesheet
https://burningseries.to/main.css
h2
609.84900000039
663.06399999303
3510
10805
200
text/css
Stylesheet
https://burningseries.to/uniform.css
h2
617.50500000198
792.64500000863
3108
11437
200
text/css
Stylesheet
https://burningseries.to/icons.css
h2
617.62299999828
729.14499999024
3588
6212
200
text/css
Stylesheet
https://www.youtube.com/s/player/2fd2ad45/www-player.css
h2
633.89699999243
668.54499999317
47892
345078
200
text/css
Stylesheet
https://www.youtube.com/s/player/2fd2ad45/www-embed-player.vflset/www-embed-player.js
h2
634.05900000362
660.48600000795
89089
287724
200
text/javascript
Script
https://www.youtube.com/s/player/2fd2ad45/player_ias.vflset/en_US/base.js
h2
634.12200001767
671.19799999637
536853
1886781
200
text/javascript
Script
https://www.youtube.com/s/player/2fd2ad45/fetch-polyfill.vflset/fetch-polyfill.js
h2
634.17999999365
644.57400000538
3586
9615
200
text/javascript
Script
https://fonts.gstatic.com/s/roboto/v18/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
h2
642.74599999771
662.74100000737
11676
10748
200
font/woff2
Font
https://www.google-analytics.com/j/collect?v=1&_v=j96&a=1934904124&t=pageview&_s=1&dl=https%3A%2F%2Fburningseries.to%2F&ul=en-us&de=UTF-8&dt=Burningseries.to%20-%20Serien%20online%20sehen%20auf%20Burning%20Series&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=YEBAAUABAAAAAC~&jid=278166217&gjid=1054258362&cid=1678721009.1646774285&tid=UA-31958500-1&_gid=152749411.1646774285&_r=1&gtm=2ou370&z=596501022
h2
721.9590000168
737.79499999364
614
1
200
text/plain
XHR
data
918.61200000858
1335.9500000079
2696
2696
200
application/x-font-ttf
Font
https://googleads.g.doubleclick.net/pagead/id
http/1.1
2007.5979999965
2635.3499999968
913
0
302
text/html
https://static.doubleclick.net/instream/ad_status.js
h2
2022.7599999926
2030.0679999928
865
29
200
text/javascript
Script
https://www.youtube.com/api/stats/qoe?cpn=tjJLhZJZpMgo495F&el=embedded&ns=yt&fexp=23858057%2C23983296%2C24001373%2C24002022%2C24002025%2C24002923%2C24004644%2C24007246%2C24080738%2C24082662%2C24134435%2C24135310%2C24167177%2C24169726&cl=432817551&seq=1&event=streamingstats&docid=bRaUrTQsyeg&cbrand=apple&cbr=Chrome&cbrver=94.0.4590.2&c=WEB_EMBEDDED_PLAYER&cver=1.20220306.00.00&cplayer=UNIPLAYER&cos=Macintosh&cosver=10_15_7&cplatform=DESKTOP&vps=0.000:N,0.000:ER&cmt=0.000:0.000,0.000:0.000&error=0.000:html5.missingapi:0.000:nocodecs.1;a6s.0&vis=0.000:0&bh=0.000:0.000
2236.9039999903
2636.0090000089
0
0
-1
Ping
https://www.google.com/js/th/b11n7QwaEucVJQMKB-LsSDNLMoQ5L9B69t4x3UT_5Ww.js
h2
2396.6639999999
2409.6540000173
14596
35881
200
text/javascript
Script
https://www.youtube.com/s/player/2fd2ad45/player_ias.vflset/en_US/embed.js
h2
2596.9479999912
2606.4670000051
8544
26617
200
text/javascript
Script
data
2602.9920000001
2603.1000000075
0
333
200
image/png
Image
https://googleads.g.doubleclick.net/pagead/id?slf_rd=1
h2
2691.5000000154
2706.6880000057
993
100
200
application/json
XHR
https://www.youtube.com/generate_204?ss3xYw
h2
3702.0740000007
3715.5090000015
224
0
204
text/plain
Image
https://www.youtube.com/youtubei/v1/log_event?alt=json&key=AIzaSyAO_FJ2SlqU8Q4STEHLGCilw_Y9_11qcW8
5794.0930000041
0
0
-1
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)
594.148
8.455
609.345
62.938
696.468
11.367
709.707
159.545
884.446
9.345
893.838
8.902
905.966
11.424
917.697
81.527
1002.832
6.546
1012.588
163.929
1180.717
5.32
1189.173
201.655
1390.856
114.204
1505.127
90.075
1595.493
17.459
1613.059
60.897
1674.536
28.449
1774.158
9.658
1793.978
507.895
2304.197
574.207
2878.458
33.366
2981.165
8.43
2989.781
7.283
2997.627
9.676
3007.434
185.398
3199.225
713.49
3998.969
9.317
4008.77
5.973
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.

Metrics

First Contentful Paint — 1.1 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 3.2 s
The time taken for the page to become fully interactive.
Speed Index — 1.8 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 2.4 s
The timing of the largest text or image that is painted.

Audits

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

Other

Properly size images — Potential savings of 427 KiB
Images can slow down the page's load time. Burningseries.to should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://burningseries.to/burningseries.png
565897
437305
Reduce unused JavaScript — Potential savings of 414 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.youtube.com/s/player/2fd2ad45/player_ias.vflset/en_US/base.js
536853
376318
https://www.youtube.com/s/player/2fd2ad45/www-embed-player.vflset/www-embed-player.js
89089
47299
Serve images in next-gen formats — Potential savings of 506 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://burningseries.to/burningseries.png
565897
517820
Reduce JavaScript execution time — 2.0 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://www.youtube.com/s/player/2fd2ad45/player_ias.vflset/en_US/base.js
1319.785
840.404
180.407
https://www.youtube.com/s/player/2fd2ad45/www-embed-player.vflset/www-embed-player.js
701.608
622.581
9.616
https://burningseries.to/
404.19
2.796
1.062
https://www.googletagmanager.com/gtag/js?id=UA-31958500-1
172.911
170.12
1.956
https://www.youtube.com/s/player/2fd2ad45/www-player.css
163.929
0
0
https://www.youtube.com/embed/bRaUrTQsyeg?start=15
156.516
88.12
3.399
Unattributable
122.198
3.114
0.22
https://www.google-analytics.com/analytics.js
82.853
60.3
0.967
Minimize main-thread work — 3.2 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
1810.573
Other
522.701
Style & Layout
238.514
Script Parsing & Compilation
204.854
Parse HTML & CSS
189.312
Garbage Collection
126.175
Rendering
68.912

Metrics

Total Blocking Time — 960 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).

Audits

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

Other

Serve static assets with an efficient cache policy — 10 resources found
Burningseries.to 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://static.doubleclick.net/instream/ad_status.js
900000
865
https://www.google-analytics.com/analytics.js
7200000
20631
https://burningseries.to/burningseries.png
14400000
566708
https://burningseries.to/icons.css
14400000
3588
https://burningseries.to/main.css
14400000
3510
https://burningseries.to/banner-styles.css
14400000
3126
https://burningseries.to/uniform.css
14400000
3108
https://burningseries.to/reset.css
14400000
2806
https://burningseries.to/screen.css
14400000
1241
https://burningseries.to/cdn-cgi/scripts/5c5dd728/cloudflare-static/email-decode.min.js
172800000
1470
Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://fonts.gstatic.com/s/roboto/v18/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
19.995000009658
Reduce the impact of third-party code — Third-party code blocked the main thread for 1,470 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)
711784
1412.096
37643
59.142
21245
0
14596
0
11676
0
2771
0
Some third-party resources can be lazy loaded with a facade — 1 facade alternative available
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Product Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
YouTube Embedded Player (Video)
711784
1412.096
Does not use passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Source
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://burningseries.to/burningseries.png
64

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of burningseries.to. 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.
`<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 alternate 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.
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"]`
Burningseries.to may provide assistance to deaf or hearing-impaired users with captions on videos.

Contrast

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
Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
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

Tables and lists

List items (`<li>`) are not 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.
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.
75

Best Practices

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

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.

Audits

Does not use HTTPS — 2 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://burningseries.to/
Allowed
http://www.burningseries.to/
Blocked

Audits

Browser errors were logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Source Description
Failed to load resource: net::ERR_ACCESS_DENIED
Issues were logged in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.
Issue type
Mixed content
SameSite cookie
82

SEO

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

Crawling and Indexing

robots.txt is not 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 burningseries.to. 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 burningseries.to 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) 57
Performance 35
Accessibility 59
Best Practices 75
SEO 85
PWA 30
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
URL: https://burningseries.to/
Updated: 8th March, 2022

1.20 seconds
First Contentful Paint (FCP)
90%
7%
3%

0.01 seconds
First Input Delay (FID)
94%
4%
2%

Simulate loading on mobile
35

Performance

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

Metrics

Cumulative Layout Shift — 0.043
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Other

Eliminate render-blocking resources
Resources, such as JavaScript and style sheets, can block the first paint of the page. Burningseries.to should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Burningseries.to should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Burningseries.to should consider minifying CSS files.
Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Burningseries.to should consider minifying JS files.
Efficiently encode images
Unoptimized images can consume more cellular data than what is necessary.
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 110 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://burningseries.to/
107.215
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Burningseries.to should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://burningseries.to/
630
https://burningseries.to/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Burningseries.to 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.
Avoids enormous network payloads — Total size was 1,356 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://burningseries.to/burningseries.png
566719
https://www.youtube.com/s/player/2fd2ad45/player_ias.vflset/en_US/base.js
536853
https://www.youtube.com/s/player/2fd2ad45/www-embed-player.vflset/www-embed-player.js
89089
https://www.youtube.com/s/player/2fd2ad45/www-player.css
47892
https://www.googletagmanager.com/gtag/js?id=UA-31958500-1
37645
https://www.youtube.com/embed/bRaUrTQsyeg?start=15
25754
https://www.google-analytics.com/analytics.js
20631
https://www.google.com/js/th/b11n7QwaEucVJQMKB-LsSDNLMoQ5L9B69t4x3UT_5Ww.js
14596
https://fonts.gstatic.com/s/roboto/v18/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
11676
https://www.youtube.com/s/player/2fd2ad45/player_ias.vflset/en_US/embed.js
8544
Avoids an excessive DOM size — 80 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
80
Maximum DOM Depth
9
Maximum Child Elements
34
Avoid chaining critical requests — 6 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Burningseries.to 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 — 3 user timings
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
Name Type Start Time (Ms) Duration (Ms)
mark_pe
Mark
669.566
mark_fs
Mark
854.501
mark_qoes
Mark
891.504
Keep request counts low and transfer sizes small — 26 requests • 1,356 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
26
1388659
Script
9
713280
Image
2
566943
Stylesheet
7
64677
Document
2
28847
Font
1
11676
Other
5
3236
Media
0
0
Third-party
16
799876
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint.
Avoid large layout shifts — 3 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.038395381481401
0.0033464379009279
0.00098835129146578
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 — 10 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://www.youtube.com/s/player/2fd2ad45/www-embed-player.vflset/www-embed-player.js
9399
564
https://www.youtube.com/s/player/2fd2ad45/player_ias.vflset/en_US/base.js
10894
529
https://www.youtube.com/s/player/2fd2ad45/player_ias.vflset/en_US/base.js
9090
309
https://www.google-analytics.com/analytics.js
3553
136
https://www.youtube.com/s/player/2fd2ad45/www-embed-player.vflset/www-embed-player.js
4440
131
https://burningseries.to/
1209
92
https://www.googletagmanager.com/gtag/js?id=UA-31958500-1
2396
77
https://burningseries.to/
1110
71
https://www.youtube.com/s/player/2fd2ad45/www-player.css
3240
61
https://www.googletagmanager.com/gtag/js?id=UA-31958500-1
2340
56
Avoid non-composited animations — 6 animated elements found
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Element Name
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 burningseries.to on mobile screens.
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.

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.

Audits

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://burningseries.to/
http/1.1
0
70.089999819174
716
0
301
text/plain
https://burningseries.to/
h2
70.8849998191
177.11399984546
3093
5446
200
text/html
Document
https://www.googletagmanager.com/gtag/js?id=UA-31958500-1
h2
203.23899993673
212.93099992909
37645
94543
200
application/javascript
Script
https://burningseries.to/banner-styles.css
h2
203.76499998383
276.01599995978
3133
11152
200
text/css
Stylesheet
https://burningseries.to/screen.css
h2
204.31900001131
330.84900001995
1227
1245
200
text/css
Stylesheet
https://burningseries.to/burningseries.png
h2
211.79399988614
282.06899994984
566719
565897
200
image/png
Image
https://burningseries.to/cdn-cgi/scripts/5c5dd728/cloudflare-static/email-decode.min.js
h2
210.33999999054
361.23099992983
1470
1239
200
application/javascript
Script
https://www.youtube.com/embed/bRaUrTQsyeg?start=15
h2
217.3049999401
283.85000000708
25754
59999
200
text/html
Document
https://www.google-analytics.com/analytics.js
h2
260.61100000516
266.41399995424
20631
50205
200
text/javascript
Script
https://www.google-analytics.com/j/collect?v=1&_v=j96&a=493069338&t=pageview&_s=1&dl=https%3A%2F%2Fburningseries.to%2F&ul=en-us&de=UTF-8&dt=Burningseries.to%20-%20Serien%20online%20sehen%20auf%20Burning%20Series&sd=24-bit&sr=360x640&vp=360x640&je=0&_u=YEBAAUABAAAAAC~&jid=1836104741&gjid=115402990&cid=2008682095.1646774310&tid=UA-31958500-1&_gid=1740821683.1646774310&_r=1&gtm=2ou370&z=1456191661
h2
340.57799982838
347.28699992411
614
1
200
text/plain
XHR
https://burningseries.to/reset.css
h2
358.96899993531
417.61499992572
2813
8418
200
text/css
Stylesheet
https://burningseries.to/main.css
h2
359.2489999719
628.73300001957
3499
10805
200
text/css
Stylesheet
https://burningseries.to/uniform.css
h2
359.62699982338
409.2309998814
2709
8818
200
text/css
Stylesheet
https://burningseries.to/icons.css
h2
360.08499981835
638.71799991466
3404
5242
200
text/css
Stylesheet
https://www.youtube.com/s/player/2fd2ad45/www-player.css
h2
365.43499981053
392.60799996555
47892
345078
200
text/css
Stylesheet
https://www.youtube.com/s/player/2fd2ad45/www-embed-player.vflset/www-embed-player.js
h2
366.47999985144
376.05899991468
89089
287724
200
text/javascript
Script
https://www.youtube.com/s/player/2fd2ad45/player_ias.vflset/en_US/base.js
h2
366.86299997382
404.76999990642
536853
1886781
200
text/javascript
Script
https://www.youtube.com/s/player/2fd2ad45/fetch-polyfill.vflset/fetch-polyfill.js
h2
367.71799996495
371.37999990955
3587
9615
200
text/javascript
Script
https://fonts.gstatic.com/s/roboto/v18/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
h2
372.71199980751
377.35799979419
11676
10748
200
font/woff2
Font
https://googleads.g.doubleclick.net/pagead/id
http/1.1
695.49499987625
726.26899997704
913
0
302
text/html
https://static.doubleclick.net/instream/ad_status.js
h2
710.22499981336
713.91299995594
865
29
200
text/javascript
Script
https://googleads.g.doubleclick.net/pagead/id?slf_rd=1
h2
727.32199984603
733.28999988735
993
100
200
application/json
XHR
data
735.33499985933
1081.8279997911
2696
2696
200
application/x-font-ttf
Font
https://www.youtube.com/api/stats/qoe?cpn=-ksR_eGV83wGOUb6&el=embedded&ns=yt&fexp=23983296%2C24001373%2C24002022%2C24002025%2C24002923%2C24004644%2C24007246%2C24080738%2C24082662%2C24135310%2C24140279%2C24154084%2C24158011%2C24164449%2C24169726%2C24175828&cl=432817551&seq=1&event=streamingstats&docid=bRaUrTQsyeg&cbrand=motorola&cbr=Chrome%20Mobile&cbrver=94.0.4590.2&c=WEB_EMBEDDED_PLAYER&cver=1.20220306.00.00&cplayer=UNIPLAYER&cmodel=moto%20g%20(4)&cos=Android&cosver=7.0&cplatform=MOBILE&vps=0.000:N,0.001:ER&cmt=0.001:0.000,0.001:0.000&error=0.001:html5.missingapi:0.000:nocodecs.1;a6s.0&vis=0.001:0&bh=0.001:0.000
894.70099983737
1085.1319998037
0
0
-1
Ping
https://www.google.com/js/th/b11n7QwaEucVJQMKB-LsSDNLMoQ5L9B69t4x3UT_5Ww.js
h2
944.3879998289
950.09099994786
14596
35881
200
text/javascript
Script
https://www.youtube.com/s/player/2fd2ad45/player_ias.vflset/en_US/embed.js
h2
1054.5599998441
1059.0559998527
8544
26617
200
text/javascript
Script
data
1060.0309998263
1060.199999949
0
333
200
image/png
Image
https://www.youtube.com/generate_204?LPAAog
h2
1401.3869999908
1411.4159999881
224
0
204
text/plain
Image
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
233.51
17.758
257.21
7.008
278.84
13.926
292.84
19.232
324.898
68.133
396.221
11.899
419.365
5.43
446.208
15.164
461.719
5.845
467.633
32.647
620.854
154.474
778.717
45.857
826.729
281.813
1108.579
15.871
1147.252
7.573
1157.746
20.453
1178.214
9.215
1190.502
264.309
1464.983
8.272
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

Reduce unused CSS — Potential savings of 45 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Burningseries.to should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.youtube.com/s/player/2fd2ad45/www-player.css
47892
46064
Reduce JavaScript execution time — 3.4 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://www.youtube.com/s/player/2fd2ad45/player_ias.vflset/en_US/base.js
1626.372
1363.384
149.648
https://www.youtube.com/s/player/2fd2ad45/www-embed-player.vflset/www-embed-player.js
1354.652
1247.156
25.196
https://www.youtube.com/embed/bRaUrTQsyeg?start=15
348.036
185.22
22.88
https://burningseries.to/
315.172
22.6
14.332
https://www.google-analytics.com/analytics.js
279.376
182.072
5.388
Unattributable
220.396
16.716
0.748
https://www.googletagmanager.com/gtag/js?id=UA-31958500-1
141.628
129.676
7.384
https://www.youtube.com/s/player/2fd2ad45/www-player.css
60.656
0
0

Metrics

First Contentful Paint — 7.0 s
The time taken for the first image or text on the page to be rendered.
Time to Interactive — 10.2 s
The time taken for the page to become fully interactive.
Speed Index — 7.0 s
The time taken for the page contents to be visibly populated.
Total Blocking Time — 630 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 — 10.4 s
The timing of the largest text or image that is painted.

Audits

Max Potential First Input Delay — 560 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 7.3 s
The time taken for the primary content of the page to be rendered.

Other

Properly size images — Potential savings of 311 KiB
Images can slow down the page's load time. Burningseries.to should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://burningseries.to/burningseries.png
565897
318409
Reduce unused JavaScript — Potential savings of 409 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://www.youtube.com/s/player/2fd2ad45/player_ias.vflset/en_US/base.js
536853
378477
https://www.youtube.com/s/player/2fd2ad45/www-embed-player.vflset/www-embed-player.js
89089
40741
Serve images in next-gen formats — Potential savings of 506 KiB
Consider JPEG 2000, JPEG XR or WebP image formats which provide better compression than PNG and JPEG.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://burningseries.to/burningseries.png
565897
517820
Serve static assets with an efficient cache policy — 10 resources found
Burningseries.to 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://static.doubleclick.net/instream/ad_status.js
900000
865
https://www.google-analytics.com/analytics.js
7200000
20631
https://burningseries.to/burningseries.png
14400000
566719
https://burningseries.to/main.css
14400000
3499
https://burningseries.to/icons.css
14400000
3404
https://burningseries.to/banner-styles.css
14400000
3133
https://burningseries.to/reset.css
14400000
2813
https://burningseries.to/uniform.css
14400000
2709
https://burningseries.to/screen.css
14400000
1227
https://burningseries.to/cdn-cgi/scripts/5c5dd728/cloudflare-static/email-decode.min.js
172800000
1470
Minimize main-thread work — 4.4 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
3180.448
Other
431.016
Style & Layout
346.004
Script Parsing & Compilation
232.812
Parse HTML & CSS
137.98
Rendering
59.092
Garbage Collection
42.456
Ensure text remains visible during webfont load
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
URL Potential Savings (Ms)
https://fonts.gstatic.com/s/roboto/v18/KFOmCnqEu92Fr1Mu4mxKKTU1Kg.woff2
4.6459999866784
Reduce the impact of third-party code — Third-party code blocked the main thread for 2,430 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)
711943
2257.92
21245
144.268
37645
23.556
14596
0
11676
0
2771
0
Some third-party resources can be lazy loaded with a facade — 1 facade alternative available
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Product Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
YouTube Embedded Player (Video)
711943
2257.92
Does not use passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Source
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://burningseries.to/burningseries.png
First Contentful Paint (3G) — 14499 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.
59

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of burningseries.to. 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.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
`<object>` elements have alternate 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.
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"]`
Burningseries.to may provide assistance to deaf or hearing-impaired users with captions on videos.

Contrast

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
Image elements do not have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
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.

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

Tables and lists

List items (`<li>`) are not 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.
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.
75

Best Practices

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

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.

Audits

Does not use HTTPS — 2 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://burningseries.to/
Allowed
http://www.burningseries.to/
Blocked

Audits

Browser errors were logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Source Description
Failed to load resource: net::ERR_ACCESS_DENIED
Issues were logged in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.
Issue type
Mixed content
SameSite cookie
85

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for burningseries.to. 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 burningseries.to on mobile screens.
Document uses legible font sizes — 99.81% legible text
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Source Selector % of Page Text Font Size
footer .btn
0.19%
11.2px
99.81%
≥ 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.
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.

Crawling and Indexing

robots.txt is not 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.
30

PWA

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

Installable

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

PWA Optimized

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

Manual Checks

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

Server Location

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

Web Hosting Provider

Name IP Address
Cloudflare, Inc.
Registration

Domain Registrant

Private Registration: No
Name:
Organization:
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:
WOT Child Safety:
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: *.burningseries.to
Issued By: E1
Valid From: 4th March, 2022
Valid To: 2nd June, 2022
Subject: CN = *.burningseries.to
Hash: 151dc047
Issuer: CN = E1
O = Let's Encrypt
S = US
Version: 2
Serial Number: 0x031DB921A04C2C8F94BEDFF69E2233E845BD
Serial Number (Hex): 031DB921A04C2C8F94BEDFF69E2233E845BD
Valid From: 4th March, 2024
Valid To: 2nd June, 2024
Signature Algorithm (Short Name): ecdsa-with-SHA384
Signature Algorithm (Long Name): ecdsa-with-SHA384
Authority Key Identifier: keyid:5A:F3:ED:2B:FC:36:C2:37:79:B9:52:30:EA:54:6F:CF:55:CB:2E:AC
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
Certificate Policies: Policy: 2.23.140.1.2.1
Policy: 1.3.6.1.4.1.44947.1.1.1
CPS: http://cps.letsencrypt.org

Authority Information Access: OCSP - URI:http://e1.o.lencr.org
CA Issuers - URI:http://e1.i.lencr.org/

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 29:79:BE:F0:9E:39:39:21:F0:56:73:9F:63:A5:77:E5:
BE:57:7D:9C:60:0A:F8:F9:4D:5D:26:5C:25:5D:C7:84
Timestamp : Mar 4 09:30:57.983 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:46:02:21:00:C7:9A:AF:D0:5F:0C:B9:C8:13:D2:32:
A8:BE:25:4F:F7:43:7E:16:F5:36:29:D3:2C:C8:62:3F:
AB:F9:63:EE:8E:02:21:00:A1:93:EA:62:83:D0:93:54:
BF:29:89:52:86:86:1A:5C:00:7A:AC:0C:33:10:46:6B:
63:8C:6B:21:85:2F:B3:5F
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : DF:A5:5E:AB:68:82:4F:1F:6C:AD:EE:B8:5F:4E:3E:5A:
EA:CD:A2:12:A4:6A:5E:8E:3B:12:C0:20:44:5C:2A:73
Timestamp : Mar 4 09:30:58.512 2022 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:45:02:21:00:F5:A5:2C:F3:78:94:B3:EE:9F:C7:22:
0E:53:BE:6A:3D:97:F9:FA:8E:64:A4:A4:CC:1B:47:9D:
D2:3E:3D:F2:DC:02:20:22:0A:34:F2:F0:0D:7A:01:89:
EF:9F:F0:53:3E:50:A8:71:11:49:32:64:A6:4B:DB:4E:
5B:82:54:0B:C0:7E:90
Key Usage: Digital Signature
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:burningseries.to
DNS:*.burningseries.to
Technical

DNS Lookup

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Date: 8th March, 2022
Content-Type: text/html
Server: cloudflare
Connection: keep-alive
Last-Modified: 11th August, 2021
Vary: Accept-Encoding
CF-Cache-Status: DYNAMIC
Expect-CT: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
Report-To: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3?s=zuRjpLNgzatlS%2BoXtIdlymJ6MkdUC6M8NgaUBMjK27hbDJtDYWQEW1JTHDAG4gFAJpff1G2U6q%2FCzSBbg7Xg16PK4bmzoeYaalXNr5K4JRAQkZpu6BYTo92%2Bwd2Oq5C9wSJp"}],"group":"cf-nel","max_age":604800}
NEL: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
CF-RAY: 6e8e99b9ee8e8cc3-EWR
alt-svc: h3=":443"; ma=86400, h3-29=":443"; ma=86400

Whois Lookup

Created:
Changed:
Expires:
Status:
Nameservers: jonah.ns.cloudflare.com
rafe.ns.cloudflare.com
Full Whois: Tonic whoisd V1.1
burningseries jonah.ns.cloudflare.com
burningseries rafe.ns.cloudflare.com

Nameservers

Name IP Address
jonah.ns.cloudflare.com 173.245.59.186
rafe.ns.cloudflare.com 108.162.192.216
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
$840 USD 1/5
$231 USD
0/5
0/5
0/5

Sites hosted on the same IP address

Domain Valuation Snoop Score
0/5
0/5