6 sec in total
1.3 sec
4.5 sec
153 ms
Click here to check amazing Lootables content for Romania. Otherwise, check out these important facts you probably never knew about lootables.com
Advanced searching of World of Warcraft's Item Database
Visit lootables.comWe analyzed Lootables.com page load time and found that the first response time was 1.3 sec and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
lootables.com performance score
name
value
score
weighting
Value1.4 s
97/100
10%
Value2.3 s
94/100
25%
Value1.4 s
100/100
10%
Value10 ms
100/100
30%
Value0
100/100
15%
Value2.3 s
99/100
10%
1327 ms
15 ms
192 ms
284 ms
287 ms
Our browser made a total of 142 requests to load all elements on the main page. We found that 59% of them (84 requests) were addressed to the original Lootables.com, 11% (16 requests) were made to Assetscdn.jivox.com and 5% (7 requests) were made to Playercdn.jivox.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Lootables.com.
Page size can be reduced by 1.1 MB (62%)
1.8 MB
686.4 kB
In fact, the total size of Lootables.com main page is 1.8 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 1.2 MB which makes up the majority of the site volume.
Potential reduce by 126.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. 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 126.6 kB or 87% of the original size.
Potential reduce by 32.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. Lootables images are well optimized though.
Potential reduce by 839.4 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 839.4 kB or 72% of the original size.
Potential reduce by 123.0 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. Lootables.com needs all CSS files to be minified and compressed as it can save up to 123.0 kB or 72% of the original size.
Number of requests can be reduced by 75 (54%)
139
64
The browser has sent 139 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lootables. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 36 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
lootables.com
1327 ms
urchin.js
15 ms
prototype.js
192 ms
scriptaculous.js
284 ms
lootables.js
287 ms
lootable.css
288 ms
WoWitem.css
290 ms
controls.css
291 ms
guide.css
288 ms
adverts.css
378 ms
adx.js
315 ms
SB_bg_top_top.gif
377 ms
SB_bg_top_bot.gif
378 ms
search_button.gif
379 ms
reset_button_disabled.gif
380 ms
SB_bg_bottom.gif
382 ms
all_main.gif
479 ms
typeHeader_end.gif
484 ms
weapons_off.gif
479 ms
armor_off.gif
484 ms
containers_off.gif
486 ms
consumables_off.gif
481 ms
trade_goods_off.gif
575 ms
projectiles_off.gif
578 ms
quivers_off.gif
576 ms
recipes_off.gif
579 ms
reagents_off.gif
581 ms
gems_off.gif
581 ms
misc_off.gif
675 ms
keys_off.gif
679 ms
quests_off.gif
676 ms
spells_off.gif
677 ms
typeFooter.gif
680 ms
INV_Axe_68.png
680 ms
tag_instance_raid_locked.png
770 ms
extSite_thottbot_med.png
773 ms
extSite_akzm_med.png
772 ms
extSite_wowhead_med.png
775 ms
addthis_widget.php
9 ms
extSite_armory_med.png
698 ms
INV_Weapon_Bow_19.png
589 ms
builder.js
594 ms
effects.js
598 ms
dragdrop.js
596 ms
controls.js
592 ms
slider.js
589 ms
INV_Mace_48.png
604 ms
INV_Sword_69.png
598 ms
INV_Staff_52.png
595 ms
INV_Weapon_Shortblade_47.png
595 ms
INV_Weapon_Glave_01.png
596 ms
tag_instance_raid.png
593 ms
INV_Weapon_Bow_31.png
595 ms
tag_none.png
586 ms
INV_Weapon_Bow_30.png
587 ms
INV_Mace_56.png
588 ms
INV_Sword_90.png
587 ms
INV_Sword_68.png
586 ms
INV_Staff_54.png
587 ms
INV_Staff_59.png
586 ms
INV_Weapon_Shortblade_62.png
585 ms
INV_Axe_84.png
586 ms
tag_arena.png
583 ms
arena_icon_small.png
585 ms
INV_Axe_60.png
586 ms
closer_off.gif
583 ms
nogold.gif
581 ms
1024override.css
375 ms
__utm.gif
7 ms
bg_pixel.gif
100 ms
landscape3.jpg
413 ms
adjs.php
130 ms
adlog.php
296 ms
ADTECH;uuid=56EEC9336E650E6EBE57969BF2B5025D;cfp=1;rndc=1458492682;loc=100;target=_blank;key=key1+key2+key3+key4;grp=[group];misc=1458492683732
8 ms
unit_renderer.php
54 ms
smart_tag.js
815 ms
moatad.js
32 ms
B9068175.122960663;dc_trk_aid=302768158;dc_trk_cid=69609815;ord=1353;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=
70 ms
tad
84 ms
layout_renderer.php
53 ms
jquery-2.1.0.min.js
53 ms
velocity.min.js
49 ms
jivoxWidgetApiV2.js
50 ms
p2
16 ms
close_24x24.png
6 ms
jivoxWidgetApiV2.js
10 ms
edge.6.0.0.min.js
45 ms
m
24 ms
pixeltracker.gif
14 ms
pixeltracker.gif
13 ms
728x90_FlashSale2016_March_edge.js
5 ms
728x90_FlashSale2016_March_edge.js
4 ms
728x90_FlashSale2016_March_edgeActions.js
4 ms
728x90_FlashSale2016_March_edgeActions.js
6 ms
bg.jpg
43 ms
bolt.svg
15 ms
number.svg
16 ms
upTo_horizontal.svg
24 ms
logo.svg
26 ms
game3.jpg
37 ms
game2.jpg
34 ms
game1.jpg
36 ms
flow2.png
35 ms
PS_Store_nobag.svg
28 ms
shoppingBag.png
33 ms
header_bar.png
99 ms
lootables_logo_large_beta.png
319 ms
a.gif
30 ms
search_button_rotate.gif
101 ms
SB_bg_top_mid.gif
100 ms
SB_bg_middle.gif
103 ms
textbox_large.png
108 ms
textbox_small.png
183 ms
SBarrow_left.gif
198 ms
SBarrow_down.gif
201 ms
typeHeader_mid.gif
180 ms
core201.js
8 ms
adjs.php
122 ms
widget020.top.svg.css
6 ms
adg.js
98 ms
show_ads.js
6 ms
adlog.php
309 ms
ca-pub-3138261370784983.js
133 ms
zrt_lookup.html
79 ms
show_ads_impl.js
79 ms
menu174.js
20 ms
footer_bg.gif
99 ms
sh200.html
28 ms
120lo.json
50 ms
ads
379 ms
osd.js
4 ms
css
60 ms
m_js_controller.js
29 ms
abg.js
31 ms
favicon
47 ms
nessie_icon_thin_arrow_big_white.png
22 ms
s
13 ms
googlelogo_color_112x36dp.png
37 ms
x_button_blue2.svg
18 ms
ui
31 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
4 ms
PuwvqkdbcqU-fCZ9Ed-b7S3USBnSvpkopQaUR-2r7iU.ttf
36 ms
lootables.com accessibility score
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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
lootables.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
lootables.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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
N/A
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lootables.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Lootables.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
lootables.com
Open Graph description is not detected on the main page of Lootables. 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: