3.7 sec in total
158 ms
3.2 sec
392 ms
Visit trivium.org now to see the best up-to-date Trivium content for Mexico and also check out these interesting facts you probably never knew about trivium.org
"The official Trivium website. New album ‘In The Court Of The Dragon’ available now
Visit trivium.orgWe analyzed Trivium.org page load time and found that the first response time was 158 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
trivium.org performance score
name
value
score
weighting
Value4.3 s
18/100
10%
Value8.0 s
2/100
25%
Value9.4 s
12/100
10%
Value3,140 ms
2/100
30%
Value0.021
100/100
15%
Value33.8 s
0/100
10%
158 ms
45 ms
113 ms
164 ms
139 ms
Our browser made a total of 157 requests to load all elements on the main page. We found that 82% of them (128 requests) were addressed to the original Trivium.org, 5% (8 requests) were made to Use.typekit.net and 3% (5 requests) were made to Libraries.wmgartistservices.com. The less responsive or slowest element that took the longest time to load (730 ms) belongs to the original domain Trivium.org.
Page size can be reduced by 1.6 MB (15%)
10.3 MB
8.7 MB
In fact, the total size of Trivium.org main page is 10.3 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. Only a small number of websites need less resources to load. Images take 8.8 MB which makes up the majority of the site volume.
Potential reduce by 404.4 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 404.4 kB or 84% of the original size.
Potential reduce by 710.9 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. Trivium images are well optimized though.
Potential reduce by 403.9 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 403.9 kB or 47% of the original size.
Potential reduce by 54.6 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. Trivium.org needs all CSS files to be minified and compressed as it can save up to 54.6 kB or 59% of the original size.
Number of requests can be reduced by 27 (19%)
140
113
The browser has sent 140 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Trivium. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
trivium.org
158 ms
www.trivium.org
45 ms
www.trivium.org
113 ms
xpg6lls.css
164 ms
otSDKStub.js
139 ms
ot.css
151 ms
launch-EN302b8a31b75a4dda8ff8df1d0cdb4762.min.js
151 ms
jquery.min.js
162 ms
jquery.cookie.min.js
127 ms
widget_min.js
160 ms
plainmailinglist.js
160 ms
validation.js
160 ms
dtm.js
160 ms
custom_js_6.js
43 ms
css_6v8QDB0pajHgSyS8p8peK43l4UNMIPurembf20My-1M.css
88 ms
css_2xJwaI_sBKQajLjnsyVJtTDml6O96fGZCusgg3GNlf4.css
98 ms
jquery-3.3.1.min.js
146 ms
js.cookie.min.js
146 ms
jquery.min.js
142 ms
vyb8yec.css
358 ms
lightbox.min.js
140 ms
main.min.js
132 ms
all.css
134 ms
custom_js_2.js
95 ms
custom_js_4.js
85 ms
custom_js_5.js
93 ms
js_LtYUh-uVobV1wtO5xYOCcBPhzwWuU2jkFPQrFkWj6h0.js
110 ms
p.css
41 ms
070263ab-649c-47b9-a8cc-76b3f5920200.json
73 ms
Desktop_BG.jpg
35 ms
Mobile_BG.png
38 ms
Trivium_Logo.svg
60 ms
close.png
32 ms
Trivium%20-%20ITCOTD%20Album_0_0.png
35 ms
Trivium_WTDMS_1080x1080.png
62 ms
phalanx.png
67 ms
yMoOqlhC-l4.jpg
41 ms
yMoOqlhC-l4.jpg
39 ms
ybekW8fZHH0.jpg
37 ms
ybekW8fZHH0.jpg
65 ms
mue8XLsKYtQ.jpg
57 ms
mue8XLsKYtQ.jpg
65 ms
gquJi978qeE.jpg
64 ms
gquJi978qeE.jpg
66 ms
8VqQPBrhmaY.jpg
65 ms
8VqQPBrhmaY.jpg
67 ms
lNgyzREsaAA.jpg
67 ms
lNgyzREsaAA.jpg
69 ms
PPNRplQnFX0.jpg
96 ms
PPNRplQnFX0.jpg
68 ms
y2xUzj0JwJ8.jpg
91 ms
y2xUzj0JwJ8.jpg
89 ms
ORe1UhIqF3c.jpg
89 ms
ORe1UhIqF3c.jpg
91 ms
GPDhXwf3RV0.jpg
94 ms
GPDhXwf3RV0.jpg
97 ms
MnjZqQhZYiY.jpg
96 ms
MnjZqQhZYiY.jpg
98 ms
RAoKcM54Q1Y.jpg
98 ms
RAoKcM54Q1Y.jpg
109 ms
Fwr1Z7uyXz4.jpg
111 ms
Fwr1Z7uyXz4.jpg
104 ms
00I-SYJaPjA.jpg
102 ms
00I-SYJaPjA.jpg
101 ms
pm-xlwkQ_qc.jpg
106 ms
location
90 ms
pm-xlwkQ_qc.jpg
81 ms
uVpU-OXrg1c.jpg
90 ms
uVpU-OXrg1c.jpg
87 ms
PcIlZ3luYHc.jpg
91 ms
PcIlZ3luYHc.jpg
89 ms
CDJkUjWJoAo.jpg
88 ms
d
52 ms
d
119 ms
d
85 ms
d
74 ms
d
73 ms
CDJkUjWJoAo.jpg
128 ms
IIvSXocE6YY.jpg
74 ms
IIvSXocE6YY.jpg
67 ms
HB_Ertr-PuQ.jpg
99 ms
HB_Ertr-PuQ.jpg
68 ms
_XD2jKlCiK0.jpg
90 ms
_XD2jKlCiK0.jpg
89 ms
2dqUqfPSDlg.jpg
92 ms
2dqUqfPSDlg.jpg
89 ms
eoUf1bbMTa8.jpg
94 ms
eoUf1bbMTa8.jpg
96 ms
UR7k3XnvbU0.jpg
92 ms
UR7k3XnvbU0.jpg
97 ms
xABUwGzfAM0.jpg
86 ms
xABUwGzfAM0.jpg
74 ms
EApnhO2OIrw.jpg
128 ms
EApnhO2OIrw.jpg
129 ms
p0u3ePdWSM4.jpg
70 ms
p0u3ePdWSM4.jpg
71 ms
Lp8p5OPtEe0.jpg
71 ms
Lp8p5OPtEe0.jpg
126 ms
oeZGGBLpbsM.jpg
129 ms
oeZGGBLpbsM.jpg
123 ms
n_L-gCy99wk.jpg
124 ms
n_L-gCy99wk.jpg
121 ms
tX226Db63ZE.jpg
121 ms
tX226Db63ZE.jpg
118 ms
2EIKvYDAM1E.jpg
120 ms
2EIKvYDAM1E.jpg
116 ms
Triv_Website.jpg
117 ms
otBannerSdk.js
37 ms
p.css
8 ms
d
94 ms
css_1gRIxBqiKSP9mhULdYJqcy3yhu7ObLkX2LZYPiIpAS0.css
11 ms
vid-play.png
38 ms
playbutton_0.png
140 ms
corey.jpg
114 ms
msg-icon.svg
110 ms
paulo.jpg
10 ms
alex.jpg
28 ms
matt.jpg
29 ms
icomoon.ttf
730 ms
fa-brands-400.ttf
210 ms
twt-x.ttf
209 ms
silenceNew.jpg
12 ms
through.jpg
15 ms
strife.jpg
40 ms
watch-wrold.jpg
42 ms
built.jpg
17 ms
waves.jpg
54 ms
shattering.jpg
43 ms
throes_0.jpg
38 ms
rising.jpg
74 ms
down.jpg
100 ms
rats.jpg
57 ms
anthem.jpg
55 ms
entrance.jpg
125 ms
likeLight.jpg
103 ms
harder.jpg
144 ms
dying.jpg
87 ms
phalanx.png
123 ms
In%20The%20Court%20Of%20The%20Dragon.jpeg
134 ms
trivium-feast.jpg
281 ms
BleedIntome.jpg
156 ms
videothumbnail_0.jpg
217 ms
Catastrophist.png
168 ms
TheWretchednessnside.jpg
280 ms
endless.jpg
191 ms
beyond.jpg
183 ms
betrayer.jpg
210 ms
thrown.jpg
210 ms
sin.jpg
231 ms
hqdefault.jpg
222 ms
dead.jpg
279 ms
until.jpg
279 ms
blind.jpg
280 ms
prev_arw.png
338 ms
next_arw.png
365 ms
icomoon.woff
709 ms
icomoon.svg
724 ms
trivium.org accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Names and labels
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.
Impact
Issue
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
trivium.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
trivium.org SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
Mobile Friendly
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/).
Impact
Issue
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Trivium.org 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 Trivium.org 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.
trivium.org
Open Graph data is detected on the main page of Trivium. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: