Access jaimebrienne.com. Jaime & Brienne Online - A community for shippers of Jaime Lannister and Brienne of Tarth.

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

10/100

10%

LCP (Largest Contentful Paint)

Value27.6 s

0/100

25%

SI (Speed Index)

Value14.1 s

1/100

10%

TBT (Total Blocking Time)

Value3,980 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.029

100/100

15%

TTI (Time to Interactive)

Value49.0 s

0/100

10%

jaimebrienne.com

44 ms

index.php

346 ms

css

89 ms

font-awesome.min.css

80 ms

jquery.min.js

86 ms

Our browser made a total of 105 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Jaimebrienne.com, 30% (31 requests) were made to Tapatalk.com and 22% (23 requests) were made to Groups.tapatalk-cdn.com. The less responsive or slowest element that took the longest time to load (907 ms) relates to the external source Cdn.pbxai.com.

Content Size

1.7 MB

After Optimization

1.4 MB

In fact, the total size of Jaimebrienne.com main page is 1.7 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 70% of websites need less resources to load. Javascripts take 954.4 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 92.9 kB

Original 116.4 kB
After minification 116.2 kB
After compression 23.5 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 92.9 kB or 80% of the original size.

Image Optimization

-2%

Potential reduce by 7.5 kB

Original 477.0 kB
After minification 469.5 kB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Jaime Brienne images are well optimized though.

JavaScript Optimization

-9%

Potential reduce by 85.4 kB

Original 954.4 kB
After minification 954.4 kB
After compression 869.0 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. This website has mostly compressed JavaScripts.

CSS Optimization

-75%

Potential reduce by 139.4 kB

Original 185.8 kB
After minification 47.4 kB
After compression 46.4 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Jaimebrienne.com needs all CSS files to be minified and compressed as it can save up to 139.4 kB or 75% of the original size.

Requests Now

After Optimization

The browser has sent 96 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Jaime Brienne. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 41 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.

Accessibility Issues

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

High

Buttons do not have an accessible name

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

Search Engine Optimization Advices

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

High

Page is blocked from indexing

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Image elements do not have [alt] attributes

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

EN
Language Claimed

EN
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jaimebrienne.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Jaimebrienne.com main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

jaimebrienne.com

Open Graph data is detected on the main page of Jaime Brienne. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook:

Report Summary

Performance

Accessibility

Best Practices

SEO

Jaime & Brienne Online - A community for shippers of Jaime Lannister and Brienne of Tarth.

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

jaimebrienne.com

index.php

css

font-awesome.min.css

jquery.min.js

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

jaimebrienne.com

index.php

css

font-awesome.min.css

jquery.min.js

gpt.js

customAdsConfig.js

default_variable.js

functions.js

en.js

check.js

adshelperpubwise.js

734de3ba-6ab2-4834-afcf-01dd1534f3ec.js

pre_pws.js

pws.js

vwpt.js

launchpad-liveramp.js

js

jquery.modal.min.css

kiosked-loader.js

tapatalk-tapatalk.js

ttg.min.js

ajaxpagination.js

moderate_tool.js

jquery.modal.min.js

payment_gold_point.js

faceMocion.css

faceMocion.js

overall_footer.js

lazysizes.min.js.js

stylesheet.css

pubads_impl.js

728035918

apstag.js

2070026-HD.jpg

KDhLFRC.jpg

12_1554361821.jpg

8_1555284660.jpg

52_1569177144.png

members-team.png

members-contact.png

pJ2lLKa.gif

StC85U9.jpg