Briansclub - Briansclub.at

Overview

Snoop Summary for briansclub.at

This is a free and comprehensive report about briansclub.at. The domain briansclub.at is currently hosted on a server located in Salt Lake City, Utah in United States with the IP address 34.106.49.194, where USD is the local currency and the local language is English. Briansclub.at has the potential to be earning an estimated $6 USD per day from advertising revenue. If briansclub.at was to be sold it would possibly be worth $4,471 USD (based on the daily revenue potential of the website over a 24 month period). Briansclub.at receives an estimated 2,144 unique visitors every day - a large amount of traffic! This report was last updated 18th May, 2021.

About briansclub.at

Site Preview:
Title:
Description:	Dumps and CVV2 Shop. The best quality cards from the Legendary Brian Krebs
Keywords and Tags:	malware or viruses, potential criminal activities, potentially illegal, privacy risk
Related Terms:	brian dumps, briansclub, briansclub cm, briansclub dumps, buy cvv2, cc dumps, cvv2 dump, dumps, fe shop cvv2, is briansclub cm legit
Fav Icon:
Age:
Domain Created:
Domain Updated:	3rd September, 2019
Domain Expires:

Review

Snoop Score

2/5

Valuation

$4,471 USD

Note: All valuation figures are estimates.

Popularity

Modest

Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank:	256,055
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:	2,144
Monthly Visitors:	65,257
Yearly Visitors:	782,560

Note: All visitors figures are estimates.

Visitors By Country

Revenue

Daily Revenue:	$6 USD
Monthly Revenue:	$186 USD
Yearly Revenue:	$2,230 USD

Note: All revenue figures are estimates.

Revenue By Country

SEO

Backlinks Analysis (SEMrush)

Top Ranking Keywords (US)

Domain Analysis

	Value	Length
Domain:	briansclub.at	13
Domain Name:	briansclub	10
Extension (TLD):	at	2

Page Speed Analysis

Average Load Time:	1.89 seconds
Load Time Comparison:	Faster than 48% of sites

Avg. (All Categories)

Performance

Accessibility

Best Practices

SEO

Progressive Web App

0–49 (Fail) 50–89 (Average) 90–100 (Pass)

Simulate loading on desktop

Performance

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

Metrics

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

Time to Interactive — 0.9 s
The time taken for the page to become fully interactive.

Total Blocking Time — 0 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).

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

Other

First CPU Idle — 0.9 s
The time taken for the page's main thread to be quiet enough to handle input.

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

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

Estimated Input Latency — 10 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive briansclub.at as laggy when the latency is higher than 0.05 seconds.

Network Requests
Below is a list of network requests that were made during page load.

URL	Protocol	Start Time (Ms)	End Time (Ms)	Transfer Size (Bytes)	Resource Size (Bytes)	Status Code	MIME Type	Resource Type
http://briansclub.at/	http/1.1	0	703.60399992205	235	0	301	text/html
https://briansclub.at/	http/1.1	704.18199989945	2569.0259998664	577	0	302	text/html
https://briansclub.at/login/	http/1.1	2569.603000069	4774.330999935	402	0	302	text/html
https://briansclub.at/login/	http/1.1	4774.9749999493	6940.2600000612	3001	8524	200	text/html	Document
https://briansclub.at/static/css/material-design-iconic-font.min.css	http/1.1	6952.4320000783	8947.6409999188	8299	70815	200	text/css	Stylesheet
https://briansclub.at/static/css/mainlogin.css	http/1.1	6952.6410000399	8899.8529999517	4975	24644	200	text/css	Stylesheet
https://briansclub.at/static/css/bootstrap.min.css	http/1.1	6952.7900000103	9149.8569999821	18456	109518	200	text/css	Stylesheet
https://briansclub.at/static/js/jquery.min.js	http/1.1	6952.9500000644	9261.3259998616	96100	95786	200	application/javascript	Script
https://briansclub.at/static/js/bootstrap.min.js	http/1.1	6953.1689998694	9056.6549999639	32132	31819	200	application/javascript	Script
https://briansclub.at/static/images/login/logo.png	http/1.1	9151.2919999659	11014.600999886	6702	6403	200	image/png	Image
https://briansclub.at/static/images/login/doc1.png	http/1.1	9267.8660000674	11739.658999955	160547	160245	200	image/png	Image
https://briansclub.at/static/images/login/doc2.png	http/1.1	9287.1570000425	11687.477000058	177401	177099	200	image/png	Image
https://briansclub.at/static/images/login/flowerpot.png	http/1.1	9287.282000063	11764.824999962	210128	209826	200	image/png	Image
https://briansclub.at/static/images/login/Three_Cards.png	http/1.1	9287.4539999757	11670.285	245351	245049	200	image/png	Image
https://briansclub.at/static/images/login/newspaper1.png	http/1.1	9287.5870000571	11721.402999945	315985	315683	200	image/png	Image
https://briansclub.at/static/images/login/A4_later.png	http/1.1	9287.861000048	11996.576000005	702706	702404	200	image/png	Image
https://briansclub.at/static/images/login/key.png	http/1.1	9287.9719999619	11539.823999861	80413	80112	200	image/png	Image
https://briansclub.at/captcha/image/62b669d293f63b93b0e63c208efda61c7649fab1/	http/1.1	9288.0799998529	11032.412	417	0	302	text/html
https://briansclub.at/static/images/login/mockup.jpg	http/1.1	9293.4870000463	11986.037999857	526879	526576	200	image/jpeg	Image
https://briansclub.at/static/fonts/GothamPro-Bold.woff	http/1.1	9295.7319999114	11388.400000054	21232	20920	200	application/font-woff	Font
https://briansclub.at/static/fonts/GothamPro.woff	http/1.1	9297.1959998831	11373.263000045	21224	20912	200	application/font-woff	Font
https://briansclub.at/static/fonts/Material-Design-Iconic-Font.woff2?v=2.2.0	http/1.1	9297.4099998828	11261.065999977	38699	38384	200	application/octet-stream	Font
https://briansclub.at/login/	http/1.1	11032.610999886	12949.367000023	2880	8306	200	text/html	Image

Show Details

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)
6970.905	7.564
9295.655	20.849
9316.516	20.986
9337.674	7.592
9345.601	6.716
12017.586	40.188
12061.037	69.029

Show Details

Diagnostics
Below is a collection of useful page vitals.
View Data

Metrics
Below is a collection of metrics.
View Data

Opportunities

Properly size images — Potential savings of 5 KiB
Images can slow down the page's load time. Briansclub.at should consider serving more appropriate-sized images.

URL	Resource Size (Bytes)	Potential Savings (Bytes)
https://briansclub.at/static/images/login/doc1.png	160245	5368

Show Details

Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Briansclub.at should consider lazy-loading offscreen and hidden images.

Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Briansclub.at should consider minifying CSS files.

Minify JavaScript
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Briansclub.at should consider minifying JS files.

Remove unused CSS — Potential savings of 17 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Briansclub.at 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://briansclub.at/static/css/bootstrap.min.css	18456	17876

Show Details

Remove unused JavaScript — Potential savings of 85 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://briansclub.at/static/js/jquery.min.js	96100	60442
https://briansclub.at/static/js/bootstrap.min.js	32132	26251

Show Details

Enable text compression — Potential savings of 84 KiB
Text-based resources should be served with compression, such as gzip, deflate or brotli.

URL	Transfer Size (Bytes)	Potential Savings (Bytes)
https://briansclub.at/static/js/jquery.min.js	95786	62520
https://briansclub.at/static/js/bootstrap.min.js	31819	23283

Show Details

Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.

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://briansclub.at/static/images/login/A4_later.png	0

Show Details

Diagnostics

Avoids enormous network payloads — Total size was 2,612 KiB
Large network payloads can cost users money and are linked to long load times.

URL	Transfer Size (Bytes)
https://briansclub.at/static/images/login/A4_later.png	702706
https://briansclub.at/static/images/login/mockup.jpg	526879
https://briansclub.at/static/images/login/newspaper1.png	315985
https://briansclub.at/static/images/login/Three_Cards.png	245351
https://briansclub.at/static/images/login/flowerpot.png	210128
https://briansclub.at/static/images/login/doc2.png	177401
https://briansclub.at/static/images/login/doc1.png	160547
https://briansclub.at/static/js/jquery.min.js	96100
https://briansclub.at/static/images/login/key.png	80413
https://briansclub.at/static/fonts/Material-Design-Iconic-Font.woff2?v=2.2.0	38699

Show Details

Avoids an excessive DOM size — 74 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		74
Maximum DOM Depth	i	8
Maximum Child Elements	PLEASE SIGN IN × authorization is required USERNAME PASSWORD SHOW PASSWOR…	12

Show Details

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. Briansclub.at 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.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://briansclub.at/login/	239.122	2.385	1.15

Show Details

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)
Rendering	138.935
Style & Layout	65.492
Other	63.842
Script Evaluation	24.378
Parse HTML & CSS	13.981
Script Parsing & Compilation	3.605

Show Details

Keep request counts low and transfer sizes small — 23 requests • 2,612 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	23	2674741
Image	10	2428992
Script	2	128232
Font	3	81155
Stylesheet	3	31730
Document	1	3001
Other	4	1631
Media	0	0
Third-party	0	0

Show Details

Minimize third-party usage
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.

Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).

Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.

Element
img

Show Details

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
PLEASE SIGN IN × authorization is required USERNAME PASSWORD SHOW PASSWOR…	0.0075539094650206
input	0.00079463872744513
	0.00021864437860221
Forgot Password? Credit Report	4.5487941991775E-5
PLEASE SIGN IN	2.521670606777E-5

Show Details

Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.

Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.

Avoid long main-thread tasks
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.

Avoid non-composited animations — 1 animated element found
It is recommended to avoid non-composited animations which are often janky and increase CLS.

Element
input

Show Details

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.

Opportunities

Eliminate render-blocking resources — Potential savings of 480 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Briansclub.at 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://briansclub.at/static/css/material-design-iconic-font.min.css	8299	70
https://briansclub.at/static/css/mainlogin.css	4975	150
https://briansclub.at/static/css/bootstrap.min.css	18456	190
https://briansclub.at/static/js/jquery.min.js	96100	310
https://briansclub.at/static/js/bootstrap.min.js	32132	230

Show Details

Efficiently encode images — Potential savings of 369 KiB
Unoptimized images can consume more cellular data than what is necessary.

URL	Resource Size (Bytes)	Potential Savings (Bytes)
https://briansclub.at/static/images/login/mockup.jpg	526576	377750

Show Details

Metrics

Speed Index — 7.1 s
The time taken for the page contents to be visibly populated.

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

Opportunities

Serve images in next-gen formats — Potential savings of 2,023 KiB
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.

URL	Resource Size (Bytes)	Potential Savings (Bytes)
https://briansclub.at/static/images/login/A4_later.png	702404	637168
https://briansclub.at/static/images/login/mockup.jpg	526576	487314
https://briansclub.at/static/images/login/newspaper1.png	315683	228559
https://briansclub.at/static/images/login/Three_Cards.png	245049	208123
https://briansclub.at/static/images/login/flowerpot.png	209826	156972
https://briansclub.at/static/images/login/doc2.png	177099	149875
https://briansclub.at/static/images/login/doc1.png	160245	136171
https://briansclub.at/static/images/login/key.png	80112	67278

Show Details

Reduce initial server response time — Root document took 2,200 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://briansclub.at/login/	2204.998

Show Details

Avoid multiple page redirects — Potential savings of 3,660 ms
Redirects can cause additional delays before the page can begin loading. Briansclub.at should avoid multiple or unnecessary page redirects.

URL	Time Spent (Ms)
http://briansclub.at/	190
https://briansclub.at/	3470
https://briansclub.at/login/	0
https://briansclub.at/login/	0

Show Details

Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Briansclub.at should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.

Diagnostics

Serve static assets with an efficient cache policy — 18 resources found
Briansclub.at 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://briansclub.at/login/	0	2880
https://briansclub.at/static/images/login/A4_later.png	604800000	702706
https://briansclub.at/static/images/login/mockup.jpg	604800000	526879
https://briansclub.at/static/images/login/newspaper1.png	604800000	315985
https://briansclub.at/static/images/login/Three_Cards.png	604800000	245351
https://briansclub.at/static/images/login/flowerpot.png	604800000	210128
https://briansclub.at/static/images/login/doc2.png	604800000	177401
https://briansclub.at/static/images/login/doc1.png	604800000	160547
https://briansclub.at/static/js/jquery.min.js	604800000	96100
https://briansclub.at/static/images/login/key.png	604800000	80413
https://briansclub.at/static/fonts/Material-Design-Iconic-Font.woff2?v=2.2.0	604800000	38699
https://briansclub.at/static/js/bootstrap.min.js	604800000	32132
https://briansclub.at/static/fonts/GothamPro-Bold.woff	604800000	21232
https://briansclub.at/static/fonts/GothamPro.woff	604800000	21224
https://briansclub.at/static/css/bootstrap.min.css	604800000	18456
https://briansclub.at/static/css/material-design-iconic-font.min.css	604800000	8299
https://briansclub.at/static/images/login/logo.png	604800000	6702
https://briansclub.at/static/css/mainlogin.css	604800000	4975

Show Details

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://briansclub.at/static/fonts/GothamPro-Bold.woff	2092.668000143
https://briansclub.at/static/fonts/GothamPro.woff	2076.0670001619
https://briansclub.at/static/fonts/Material-Design-Iconic-Font.woff2?v=2.2.0	1963.6560000945

Show Details

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	Failing Elements
https://briansclub.at/static/images/login/A4_later.png	img
https://briansclub.at/static/images/login/Three_Cards.png	img
https://briansclub.at/static/images/login/doc2.png	img
https://briansclub.at/static/images/login/doc1.png	img
https://briansclub.at/static/images/login/key.png	img
https://briansclub.at/static/images/login/logo.png	img
https://briansclub.at/captcha/image/62b669d293f63b93b0e63c208efda61c7649fab1/	captcha

Show Details

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of briansclub.at. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.

The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.

`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.

Heading elements appear in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.

No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.

`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.

`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.

`[aria-hidden="true"]` elements do not contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.

ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.

ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.

ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.

`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.

Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.

`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.

`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.

ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.

ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.

ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.

`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.

`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.

ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.

No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.

Failing Elements
input

Show Details

`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.

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

`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.

Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.

`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.

Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.

Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.

List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.

Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.

`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.

`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.

`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Briansclub.at 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
USERNAME
input
PASSWORD
input
SHOW PASSWORD
input

Show Details

Names and labels

Form elements do not have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.

Failing Elements
input

Show Details

Best practices

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

Failing Elements
meta

Show Details

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.

Best Practices

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

Passing (16)
Failing (2)

Audits

Links to cross-origin destinations are safe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.

Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.

Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.

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.

Avoids Application Cache
Application cache is deprecated and is no longer recommended.

Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.

Name	Version
Bootstrap	3.2.0
jQuery	1.11.1

Show Details

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://briansclub.at/	Allowed

Show Details

Includes front-end JavaScript libraries with known security vulnerabilities — 9 vulnerabilities detected
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.

Library Version	Vulnerability Count	Highest Severity
SHOW DETAILS	5	Medium
SHOW DETAILS	4	Medium

Show Details

SEO

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

Document uses legible font sizes
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.

Tap targets are sized appropriately
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.

Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.

Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.

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

Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.

Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.

Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.

Links are crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.

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 — 166 errors found
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Line #	Content	Error
4	<!DOCTYPE html>	Syntax not understood
5	<html lang="en">	Syntax not understood
6	<head>	Syntax not understood
7	<meta charset="UTF-8">	Syntax not understood
8	<meta name="viewport"	Syntax not understood
9	content="width=device-width, user-scalable=no, initial-scale=1.0, maximum-scale=1.0, minimum-scale=1.0">	Syntax not understood
10	<meta http-equiv="X-UA-Compatible" content="ie=edge">	Syntax not understood
11	<meta name="description" content="Dumps and CVV2 Shop. The best quality cards from the Legendary Brian Krebs">	Syntax not understood
12	<meta name="author" content="Brian Krebs">	Syntax not understood
13	<meta http-equiv="onion-location" content="http://briansccxf4qknms.onion">	Unknown directive
14	<meta name="n" content="3">	Syntax not understood
16	<title>Welcome!</title>	Syntax not understood
17	<link href="/static/images/favicon_v3.ico" rel="icon" type="image/x-icon">	Syntax not understood
18	<link href="/static/images/favicon_v3.ico" rel="shortcut" type="image/x-icon">	Syntax not understood
19	<title>BriansClub - Sign In.</title>	Syntax not understood
20	<!-- Chrome, Firefox OS and Opera -->	Syntax not understood
21	<meta name="theme-color" content="#000">	Syntax not understood
22	<!-- Windows Phone -->	Syntax not understood
23	<meta name="msapplication-navbutton-color" content="#000">	Syntax not understood
24	<!-- iOS Safari -->	Syntax not understood
25	<meta name="apple-mobile-web-app-status-bar-style" content="#000">	Syntax not understood
26	<link rel="stylesheet" href="/static/css/material-design-iconic-font.min.css">	Syntax not understood
27	<link rel="stylesheet" href="/static/css/mainlogin.css">	Syntax not understood
29	<!-- Custom styles for this template -->	Syntax not understood
30	<!-- <link href="/static/css/signin.css" rel="stylesheet"> -->	Syntax not understood
31	<!-- Bootstrap core CSS -->	Syntax not understood
32	<link href="/static/css/bootstrap.min.css" rel="stylesheet">	Syntax not understood
33	<script src="/static/js/jquery.min.js"></script>	Syntax not understood
34	<script src="/static/js/bootstrap.min.js"></script>	Syntax not understood
36	</head>	Syntax not understood
37	<body>	Syntax not understood
38	<noscript>	Syntax not understood
39	<div class="alert alert-danger fade in" style='text-align: center;font-size:15pt;' tabindex="-1">	Unknown directive
40	<p>Please enable Javascript to continue.</p>	Syntax not understood
41	</div>	Syntax not understood
42	</noscript>	Syntax not understood
44	<section class="form-section" id="form-section" style="background-image: url(/static/images/login/mockup-1.jpg);">	Unknown directive
46	<div class="form-decorations" >	Syntax not understood
47	<div class="form-decorations__logo form-decorations__item">	Syntax not understood
48	<img src="/static/images/login/logo.png" alt="">	Syntax not understood
49	</div>	Syntax not understood
50	<div class="form-decorations__item">	Syntax not understood
51	<img src="/static/images/login/doc1.png" alt="">	Syntax not understood
52	</div>	Syntax not understood
53	<div class="form-decorations__item">	Syntax not understood
54	<img src="/static/images/login/doc2.png" alt="">	Syntax not understood
55	</div>	Syntax not understood
56	<div class="form-decorations__item">	Syntax not understood
57	<img src="/static/images/login/flowerpot.png" alt="">	Syntax not understood
58	</div>	Syntax not understood
59	<div class="form-decorations__item">	Syntax not understood
60	<img src="/static/images/login/Three_Cards.png" alt="">	Syntax not understood
61	</div>	Syntax not understood
62	<div class="form-decorations__item">	Syntax not understood
63	<img src="/static/images/login/newspaper1.png" alt="">	Syntax not understood
64	</div>	Syntax not understood
65	<div class="form-decorations__item">	Syntax not understood
66	<img src="/static/images/login/A4_later.png" alt="">	Syntax not understood
67	</div>	Syntax not understood
68	<div class="form-decorations__item">	Syntax not understood
69	<img src="/static/images/login/key.png" alt="">	Syntax not understood
70	</div>	Syntax not understood
71	</div>	Syntax not understood
73	<div class="form-wrapper container">	Syntax not understood
75	<form class="form form-signin" id="form-sing-in" action="/login/" method="post" role="form" >	Syntax not understood
76	<input type='hidden' name='csrfmiddlewaretoken' value='nHvSVkoqFhXvJcCwVu3Fy9ocTwAV9wwn' />	Syntax not understood
78	<h3 class="form-title">	Syntax not understood
79	<span>	Syntax not understood
80	Please sign in	Syntax not understood
81	</span>	Syntax not understood
82	</h3>	Syntax not understood
87	<div class="alert alert-danger alert-danger-page fade in" style='display:none;margin-top:10px;' tabindex="-1">	Unknown directive
88	<button type="button" class="close" data-dismiss="alert">×</button>	Syntax not understood
89	<p id='pageDanger'></p>	Syntax not understood
90	</div>	Syntax not understood
91	<div class="alert alert-block alert-success alert-success-page fade in" style='display:none;margin-top:10px;'	Unknown directive
92	tabindex="-1">	Syntax not understood
93	<button type="button" class="close" data-dismiss="alert">×</button>	Syntax not understood
94	<p id='pageSuccess'></p>	Syntax not understood
95	</div>	Syntax not understood
96	<div class="alert alert-block alert-info alert-info-page fade in" style='display:none;margin-top:30px;' tabindex="-1">	Unknown directive
97	<button type="button" class="close" data-dismiss="alert">×</button>	Syntax not understood
98	<p id='pageInfo'></p>	Syntax not understood
99	</div>	Syntax not understood
102	<div class="form-group">	Syntax not understood
103	<label for="id_username" class="form__label control-label">Username</label>	Syntax not understood
104	<div class="form-group__wrapper form-group">	Syntax not understood
105	<input required type="text" id="id_username" name="username" placeholder="Username" maxlength="32" required="required" class="form__input">	Syntax not understood
106	<span class="form-group__icon">	Syntax not understood
107	<i class="zmdi zmdi-account"></i>	Syntax not understood
108	</span>	Syntax not understood
109	</div>	Syntax not understood
110	</div>	Syntax not understood
112	<div class="form-group">	Syntax not understood
113	<label for="password" class="form__label">Password</label>	Syntax not understood
114	<div class="form-group__wrapper form-group">	Syntax not understood
115	<input type="password" id="password" name="password" maxlength="64" placeholder="Password" required="required" class="form__input">	Syntax not understood
116	<span class="form-group__icon">	Syntax not understood
117	<i class="zmdi zmdi-account"></i>	Syntax not understood
118	</span>	Syntax not understood
119	</div>	Syntax not understood
120	<input type="checkbox" onclick="ShowPassword()" class="form__label"> <label for="password" class="form__label">Show Password </label>	Syntax not understood
121	</div>	Syntax not understood
124	<div class="form-group captcha-wrapper" style="margin-top: 20px;">	Unknown directive
125	<!-- <label for="code" class="form__label">enter code</label> -->	Syntax not understood
126	<div class="form-group__wrapper" style="display: ruby-text-container;">	Unknown directive
127	<img src="/captcha/image/0b87cc667d985be6ec383dcabad1e6913af8366e/" alt="captcha" class="captcha" /> <input id="id_captcha_0" name="captcha_0" type="hidden" value="0b87cc667d985be6ec383dcabad1e6913af8366e" /> <input autocomplete="off" id="id_captcha_1" name="captcha_1" type="text" />	Syntax not understood
128	<span class="form-group__captcha" id="captcha"></span>	Syntax not understood
129	</div>	Syntax not understood
130	</div>	Syntax not understood
133	<div class="form-buttons">	Syntax not understood
134	<button class="button form__button form__button--gradient" type="submit">Login</button>	Syntax not understood
135	<a href="/register" class="button form__button ">Register</a>	Syntax not understood
136	</div>	Syntax not understood
138	<div class="form-links">	Syntax not understood
139	<a href="#modalReset" class="form-links__item" data-toggle="modal">Forgot Password?</a>	Syntax not understood
140	<a href="/static/credit_report.pdf" target="_blank" class="form-links__item">Credit Report</a>	Syntax not understood
141	</div>	Syntax not understood
142	</form>	Syntax not understood
143	</div>	Syntax not understood
145	<div class="modal fade" id="modalReset" tabindex="-1" role="dialog">	Syntax not understood
146	<div class="modal-dialog">	Syntax not understood
147	<div class="modal-content">	Syntax not understood
148	<div class="modal-header">	Syntax not understood
149	<button type="button" class="close" data-dismiss="modal"><span aria-hidden="true">×</span><span class="sr-only">Close</span></button>	Syntax not understood
150	<h4 class="modal-title" id="modalResetTitle">Reset Password</h4>	Syntax not understood
151	</div>	Syntax not understood
152	<div class="modal-body">	Syntax not understood
153	Please create a new account and submit a ticket requesting password reset for your original account.	Syntax not understood
154	</div>	Syntax not understood
155	<div class="modal-footer">	Syntax not understood
156	<button type="button" class="btn btn-default" data-dismiss="modal">Close</button>	Syntax not understood
157	</div>	Syntax not understood
158	</div>	Syntax not understood
159	</div>	Syntax not understood
160	</div>	Syntax not understood
161	</section>	Syntax not understood
164	<script>	Syntax not understood
165	$(document).ready(function () {	Syntax not understood
166	$("#id_captcha_1").attr('class', 'form__input');	Syntax not understood
167	$("#id_captcha_1").attr('required', 'required');	Syntax not understood
168	$("#id_captcha_1").attr('placeholder', 'Equals?');	Syntax not understood
169	$("#id_captcha_1").css("width", "auto");	Syntax not understood
170	$("#id_username").keypress(function(event){	Syntax not understood
171	var ew = event.which;	Syntax not understood
172	if(48 <= ew && ew <= 57)	Syntax not understood
173	return true;	Syntax not understood
174	if(65 <= ew && ew <= 90)	Syntax not understood
175	return true;	Syntax not understood
176	if(97 <= ew && ew <= 122)	Syntax not understood
177	return true;	Syntax not understood
178	return false;	Syntax not understood
179	});	Syntax not understood
180	})	Syntax not understood
181	function ShowPassword() {	Syntax not understood
182	var x = $("#password");	Syntax not understood
183	if (x.attr("type") === "password") {	Syntax not understood
184	x.attr("type","text");	Syntax not understood
185	} else {	Syntax not understood
186	x.attr("type","password");	Syntax not understood
187	}	Syntax not understood
188	};	Syntax not understood
189	</script>	Syntax not understood
191	</body>	Syntax not understood
193	<!-- <script src="/static/js/bundle.js"></script> -->	Syntax not understood
195	</html>	Syntax not understood

Show Details

Progressive Web App

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

PWA Optimized

Redirects HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.

Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of briansclub.at 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

Show Details

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)

Performance

Accessibility

Best Practices

SEO

Progressive Web App

0–49 (Fail) 50–89 (Average) 90–100 (Pass)

Simulate loading on mobile

Performance

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

Metrics

Time to Interactive — 3.2 s
The time taken for the page to become fully interactive.

Total Blocking Time — 30 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).

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

Other

First CPU Idle — 3.4 s
The time taken for the page's main thread to be quiet enough to handle input.

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

Estimated Input Latency — 10 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive briansclub.at as laggy when the latency is higher than 0.05 seconds.

Network Requests
Below is a list of network requests that were made during page load.

URL	Protocol	Start Time (Ms)	End Time (Ms)	Transfer Size (Bytes)	Resource Size (Bytes)	Status Code	MIME Type	Resource Type
http://briansclub.at/	http/1.1	0	469.04900006484	250	0	301	text/html
https://briansclub.at/	http/1.1	469.72100005951	2336.3380000228	577	0	302	text/html
https://briansclub.at/login/	http/1.1	2336.8780000601	4230.951000005	3006	8524	200	text/html	Document
https://briansclub.at/static/css/material-design-iconic-font.min.css	http/1.1	4248.9840000635	6234.2430000426	8299	70815	200	text/css	Stylesheet
https://briansclub.at/static/css/mainlogin.css	http/1.1	4249.1830000654	6197.9600000195	4975	24644	200	text/css	Stylesheet
https://briansclub.at/static/css/bootstrap.min.css	http/1.1	4249.3729999987	6420.288000023	18456	109518	200	text/css	Stylesheet
https://briansclub.at/static/js/jquery.min.js	http/1.1	4249.6400000528	6569.1430000588	96100	95786	200	application/javascript	Script
https://briansclub.at/static/js/bootstrap.min.js	http/1.1	4249.9020000687	6389.1330000479	32132	31819	200	application/javascript	Script
https://briansclub.at/static/images/login/logo.png	http/1.1	6421.7730000382	8301.753000007	6702	6403	200	image/png	Image
https://briansclub.at/static/images/login/doc1.png	http/1.1	6576.9070000388	8978.6869999953	160547	160245	200	image/png	Image
https://briansclub.at/static/images/login/doc2.png	http/1.1	6603.6150000291	9055.876999977	177401	177099	200	image/png	Image
https://briansclub.at/static/images/login/flowerpot.png	http/1.1	6603.8539999863	8943.3590000262	210128	209826	200	image/png	Image
https://briansclub.at/static/images/login/Three_Cards.png	http/1.1	6604.1409999598	8972.8469999973	245351	245049	200	image/png	Image
https://briansclub.at/static/images/login/newspaper1.png	http/1.1	6604.6410000417	9146.3089999743	315985	315683	200	image/png	Image
https://briansclub.at/static/images/login/A4_later.png	http/1.1	6604.8139999621	9274.5560000185	702706	702404	200	image/png	Image
https://briansclub.at/static/images/login/key.png	http/1.1	6604.9529999727	8937.3739999719	80413	80112	200	image/png	Image
https://briansclub.at/captcha/image/7fb7354931106fa6e955596077b7f64b5bdb5008/	http/1.1	6605.1000000443	8315.8609999809	417	0	302	text/html
https://briansclub.at/static/images/login/mockup.jpg	http/1.1	6613.6440000264	9267.4780000234	526879	526576	200	image/jpeg	Image
https://briansclub.at/static/fonts/GothamPro-Bold.woff	http/1.1	6614.3079999601	8544.5420000469	21232	20920	200	application/font-woff	Font
https://briansclub.at/static/fonts/GothamPro.woff	http/1.1	6616.4839999983	8760.2160000242	21224	20912	200	application/font-woff	Font
https://briansclub.at/static/fonts/Material-Design-Iconic-Font.woff2?v=2.2.0	http/1.1	6616.8489999836	8678.5369999707	38699	38384	200	application/octet-stream	Font
https://briansclub.at/login/	http/1.1	8316.2749999901	10227.807000047	2885	8306	200	text/html	Image

Show Details

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)
4265.119	10.798
6607.524	27.658
6635.197	30.286
6665.555	5.052
6670.841	9.282
6680.467	9.701
6690.936	6.816
9308.399	36.309

Show Details

Diagnostics
Below is a collection of useful page vitals.
View Data

Metrics
Below is a collection of metrics.
View Data

Opportunities

Properly size images
Images can slow down the page's load time. Briansclub.at should consider serving more appropriate-sized images.