10.2 sec in total
663 ms
9.3 sec
238 ms
Visit rift.curseforge.com now to see the best up-to-date Rift Curse Forge content for China and also check out these interesting facts you probably never knew about rift.curseforge.com
Visit rift.curseforge.comWe analyzed Rift.curseforge.com page load time and found that the first response time was 663 ms and then it took 9.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
rift.curseforge.com performance score
name
value
score
weighting
Value5.7 s
5/100
10%
Value8.0 s
3/100
25%
Value5.8 s
50/100
10%
Value370 ms
71/100
30%
Value0.095
91/100
15%
Value10.1 s
26/100
10%
663 ms
12 ms
8 ms
51 ms
50 ms
Our browser made a total of 266 requests to load all elements on the main page. We found that 2% of them (5 requests) were addressed to the original Rift.curseforge.com, 32% (85 requests) were made to Idsync.rlcdn.com and 4% (11 requests) were made to Cm.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (5.4 sec) relates to the external source Ibla2.ib-ibi.com.br.
Page size can be reduced by 351.6 kB (45%)
785.8 kB
434.2 kB
In fact, the total size of Rift.curseforge.com main page is 785.8 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 50% of websites need less resources to load. Images take 330.5 kB which makes up the majority of the site volume.
Potential reduce by 17.6 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. This page needs HTML code to be minified as it can gain 6.9 kB, which is 30% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 17.6 kB or 77% of the original size.
Potential reduce by 13.8 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. Rift Curse Forge images are well optimized though.
Potential reduce by 177.3 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 177.3 kB or 66% of the original size.
Potential reduce by 142.8 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. Rift.curseforge.com needs all CSS files to be minified and compressed as it can save up to 142.8 kB or 86% of the original size.
Number of requests can be reduced by 197 (92%)
215
18
The browser has sent 215 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Rift Curse Forge. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and as a result speed up the page load time.
rift.curseforge.com
663 ms
curseforge.css
12 ms
footer.css
8 ms
base.js
51 ms
footer.js
50 ms
curseforge-logo.png
89 ms
curse-logo.png
77 ms
icon-social-links.png
68 ms
featured-gw2g.png
72 ms
featured-lolpro.png
68 ms
featured-mmoc.png
74 ms
featured-gw2db.png
72 ms
icon-back_to_top.png
69 ms
444444ff-44444400.png
78 ms
system-search.png
75 ms
676767ff-414141ff.png
79 ms
484848ff-222222ff.png
73 ms
414141ff-41414100.png
75 ms
222222ff-22222200.png
79 ms
internet-group-chat.png
76 ms
curseforge-background-optimized.jpg
63 ms
ui-bg_flat_75_ffffff_40x100.png
21 ms
ga.js
29 ms
beacon.js
6 ms
cc.js
61 ms
c=3613
12 ms
__utm.gif
18 ms
__utm.gif
14 ms
m
22 ms
rt=ifr
16 ms
px
10 ms
bk-static.js
80 ms
bcP.js
9 ms
pibiview.js
5414 ms
pibiview.js
66 ms
var=lotjson
9 ms
pibiview.js
96 ms
pibiview.js
208 ms
pibiview.js
94 ms
10 ms
ca.html
9 ms
datapair
50 ms
datapair
46 ms
pixel
46 ms
Pug
50 ms
cx
52 ms
rum
42 ms
adb.gif
30 ms
1
51 ms
cs
361 ms
sync
38 ms
30 ms
30 ms
31 ms
Pix-1x1.gif
28 ms
demconf.jpg
13 ms
xrefid.xgi
19 ms
cm
23 ms
tap.php
24 ms
22 ms
sd
20 ms
360947.gif
23 ms
rum
52 ms
pixel
26 ms
18 ms
cm
16 ms
pixel
15 ms
mapuid
18 ms
lr.gif
138 ms
cm
7 ms
xrefid.xgi
12 ms
cm
7 ms
362378.gif
10 ms
cx
16 ms
pixel.gif
6 ms
pixel.gif
7 ms
120 ms
120 ms
cx
14 ms
ibiview.js
3091 ms
ibiview.js
148 ms
get
31 ms
127121.html
28 ms
ibiview.js
14 ms
ibiview.js
40 ms
ibiview.js
208 ms
at.js
26 ms
seg=152589
32 ms
ca.html
17 ms
127121.html
47 ms
at.js
136 ms
pixel
22 ms
tap.php
218 ms
Pug
1037 ms
rum
107 ms
sd
12 ms
adb.gif
14 ms
1
32 ms
cs
338 ms
image.ibvp
33 ms
cm
17 ms
Pix-1x1.gif
19 ms
cm
18 ms
pixel
18 ms
generic
14 ms
cm
14 ms
info.php
168 ms
generic
5 ms
362588.gif
14 ms
378348.gif
11 ms
362358.gif
11 ms
362708.gif
6 ms
generic
5 ms
id
20 ms
at.js
24 ms
362248.gif
16 ms
3PDPHandler.aspx
48 ms
3PDPHandler.aspx
143 ms
at.js
318 ms
3PDPHandler.aspx
9 ms
lrpush.apxlv.com
42 ms
gif
26 ms
362248.gif
15 ms
362378.gif
15 ms
adsct
99 ms
gpush.cogocast.net
38 ms
p90
16 ms
367408.gif
15 ms
362408.gif
10 ms
GenericUserSync.ashx
28 ms
pixel
21 ms
pm_match
8 ms
378298.gif
13 ms
gpush.cogocast.net
17 ms
pm_match
11 ms
379848.gif
10 ms
378298.gif
10 ms
366818.gif
14 ms
65 ms
liveramp
52 ms
redirect
50 ms
382666.gif
8 ms
360787.gif
12 ms
379718.gif
53 ms
395596.gif
17 ms
382189.gif
24 ms
361576.gif
15 ms
366438.gif
18 ms
p
12 ms
364708.gif
11 ms
378488.gif
11 ms
377988.gif
9 ms
380008.gif
16 ms
362278.gif
33 ms
384206.gif
32 ms
liveramp
13 ms
127121.gif
11 ms
397716.gif
28 ms
idsynch.php
31 ms
check
24 ms
utsync.ashx
200 ms
382149.gif
12 ms
366838.gif
14 ms
i.match
165 ms
360947.gif
16 ms
362318.gif
18 ms
397176.gif
30 ms
090f02778648e6a615f8ecda1f5beb42d64a51612af258335b7872e7520b1d2bd73ff78b4400b324
58 ms
364698.gif
20 ms
ds.png
101 ms
383826.gif
14 ms
cse
131 ms
394386.gif
12 ms
utsync.ashx
13 ms
i.match
92 ms
378388.gif
10 ms
liveramp
11 ms
382159.gif
12 ms
378248.gif
15 ms
8 ms
378718.gif
11 ms
blank.gif
8 ms
sync
27 ms
382779.gif
19 ms
lr.gif
6 ms
382129.gif
16 ms
383876.gif
27 ms
1380_03644
30 ms
cepgahefiemebepgmgbgjfad.gif
85 ms
380759.gif
10 ms
dc.optimahub.com
373 ms
384196.gif
10 ms
LiveRamp.ashx
107 ms
387496.gif
16 ms
401336.gif
17 ms
384996.gif
21 ms
387016.gif
20 ms
395586.gif
15 ms
379488.gif
26 ms
396846.gif
22 ms
396766.gif
13 ms
395806.gif
17 ms
pixel
20 ms
sync
32 ms
362358.gif
11 ms
397026.gif
23 ms
397596.gif
18 ms
liverampuid
104 ms
$397796.gif
209 ms
img;m=11022202176866;cache=
50 ms
396926.gif
18 ms
386676.gif
12 ms
127121.gif
21 ms
dptr
19 ms
track.png
12 ms
id
43 ms
398536.gif
35 ms
pixel
28 ms
cm
22 ms
match
17 ms
402046.gif
25 ms
402096.gif
26 ms
362358.gif
19 ms
402896.gif
22 ms
403466.gif
26 ms
lrs.gif
236 ms
pixel
21 ms
pixel
19 ms
pixel
54 ms
362358.gif
16 ms
362358.gif
25 ms
362358.gif
20 ms
image.sbxx
236 ms
img
16 ms
img;m=11022202176866;cache=
44 ms
398526.gif
24 ms
405436.gif
23 ms
366598.gif
18 ms
px
19 ms
382389.gif
32 ms
384126.gif
42 ms
385566.gif
38 ms
image.sbxx
143 ms
377728.gif
13 ms
elr
12 ms
366458.gif
9 ms
ecc
8 ms
140601.gif
18 ms
activity;src=1901398;type=lrmp;cat=dmp02;u2=9302ae0bc88f549aa9c1aedddcfe3b4cd6182fe08680812026b625a651f01063a6704fcfe29d7ba7
15 ms
127121.gif
44 ms
387006.gif
30 ms
cb,58260695
35 ms
lr
192 ms
in
37 ms
367148.gif
25 ms
382686.gif
18 ms
401726.gif
36 ms
sync
222 ms
1
33 ms
at-int.gif
68 ms
52154.gif
28 ms
127121.gif
15 ms
14747
39 ms
381919.gif
28 ms
47154.gif
41 ms
rum
31 ms
rift.curseforge.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Some elements have a [tabindex] value greater than 0
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
Image elements do not have [alt] attributes
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.
rift.curseforge.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
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
Issues were logged in the Issues panel in Chrome Devtools
rift.curseforge.com 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Rift.curseforge.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 Rift.curseforge.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.
rift.curseforge.com
Open Graph description is not detected on the main page of Rift Curse Forge. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: