3.1 sec in total
394 ms
2.1 sec
582 ms
Click here to check amazing Wiz Army 11 Alive content for United States. Otherwise, check out these important facts you probably never knew about wizarmy.11alive.com
Visit wizarmy.11alive.comWe analyzed Wizarmy.11alive.com page load time and found that the first response time was 394 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
wizarmy.11alive.com performance score
name
value
score
weighting
Value1.9 s
87/100
10%
Value2.5 s
90/100
25%
Value2.4 s
98/100
10%
Value10 ms
100/100
30%
Value0
100/100
15%
Value2.7 s
97/100
10%
394 ms
104 ms
116 ms
104 ms
121 ms
Our browser made a total of 115 requests to load all elements on the main page. We found that 3% of them (3 requests) were addressed to the original Wizarmy.11alive.com, 30% (35 requests) were made to Awsmedia.dtsph.com and 16% (18 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (491 ms) relates to the external source Scontent.xx.fbcdn.net.
Page size can be reduced by 1.0 MB (54%)
1.9 MB
872.3 kB
In fact, the total size of Wizarmy.11alive.com main page is 1.9 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.1 MB which makes up the majority of the site volume.
Potential reduce by 74.1 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 74.1 kB or 80% of the original size.
Potential reduce by 12.1 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. Wiz Army 11 Alive images are well optimized though.
Potential reduce by 716.8 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 716.8 kB or 65% of the original size.
Potential reduce by 221.9 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. Wizarmy.11alive.com needs all CSS files to be minified and compressed as it can save up to 221.9 kB or 81% of the original size.
Number of requests can be reduced by 59 (55%)
107
48
The browser has sent 107 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wiz Army 11 Alive. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 38 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
wizarmy.11alive.com
394 ms
272647f3ed09409ee229cab5b3631c91_1.css
104 ms
css_41e3fe94bb326d3ace9c77d17454785f_0.css
116 ms
css_f8ba777d5b80b45c12661f3e6200c18f_0.css
104 ms
css_b2f810b10acdedff6f5bdb7163bcdee6_0.css
121 ms
css_bef15dfcf5ab899c9a105a161df161a0_0.css
122 ms
css_0fcfd7b479a7298125cb8748ba3f1eb5_0.css
121 ms
css_a7683311501f59f74866eb9925d965d8_2.css
122 ms
css_ed240a79d2d5e8c1ab51ab6a7ae77cd8_19.css
124 ms
css_0b88ebcdc206472122b30156adb01666_0.css
128 ms
css_c80aed1815a97bf5d8f787db29c9e718_0.css
126 ms
jquery.min.js
30 ms
jquery-ui.min.js
51 ms
js_346572f32bc065f3ed47c2a33bddf9f8_0.js
143 ms
js_7ba931ce633db32cb795cf62cd89545d_1.js
145 ms
js_40af8046e886469b17b0b2a64b9fc207_6.js
145 ms
js_9282c8d02fe688b2f667398688e99425_0.js
151 ms
font-awesome.min.css
5 ms
feed.gbmap
56 ms
s_code_go4.js
152 ms
1743488083@x96
219 ms
js_8059f6b00f4cd45b42f515041b28da70_0.js
79 ms
s_site_specific_code.js
84 ms
purim-carnival-silent-auction-14.jpeg
28 ms
nedogoabe3yT_01.jpg
227 ms
feed.gbmap
28 ms
beacon.js
15 ms
wizarmy-header.png
18 ms
default-sprite.png
18 ms
11alive_logo.jpg
17 ms
635638585907619416-Still0405-00001jpg.jpg
16 ms
635599817466816516-homeless1jpg.jpg
17 ms
octane_-_copy.jpg
16 ms
atlanta%20skyline.jpg
19 ms
fulcologo3%20jpg_39.jpg
19 ms
Fulton%20County%20Logo_1.jpg
18 ms
635558883509741891-Still0103-00000jpg.jpg
21 ms
52780137_1.jpg
22 ms
claudiostornellidallas.jpg
19 ms
ericaswedelson.jpg
23 ms
michellebrugh.jpg
23 ms
1.jpeg
25 ms
pollenrecord.jpg
24 ms
buch.jpg
25 ms
erichill.jpg
24 ms
113309496.jpg
25 ms
s_code_go4.js
68 ms
wiz_only.jpg
201 ms
radar_for_mobile.jpg
190 ms
gb.aspx
68 ms
css_ded5894e7183964f72b656c2eeff7bf7_1.css
47 ms
likebox.php
476 ms
fontawesome-webfont.woff
13 ms
GoogleMapGasPrices.js
108 ms
js
149 ms
prototype.ashx
109 ms
core.ashx
112 ms
converter.ashx
111 ms
AdventMapsServer.GB_Google,AdventMapsServer.ashx
111 ms
empty.gif
153 ms
s59697449367959
85 ms
dc.js
89 ms
ajax
483 ms
__utm.gif
37 ms
common.js
19 ms
map.js
38 ms
util.js
63 ms
geocoder.js
60 ms
StaticMapService.GetMapImage
122 ms
onion.js
17 ms
ViewportInfoService.GetViewportInfo
62 ms
stats.js
32 ms
controls.js
28 ms
transparent.png
82 ms
t.aspx
79 ms
t.aspx
76 ms
t.aspx
80 ms
t.aspx
79 ms
css
105 ms
infowindow.js
45 ms
marker.js
37 ms
google4.png
35 ms
mapcnt6.png
49 ms
tmapctrl.png
35 ms
cb_scout5.png
46 ms
tmapctrl4.png
45 ms
imgs8.png
46 ms
vt
24 ms
vt
20 ms
vt
13 ms
vt
33 ms
vt
15 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
32 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
38 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
49 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
53 ms
AuthenticationService.Authenticate
28 ms
hDvwL1_H7g-.css
179 ms
56WNbrUYLbL.css
221 ms
xxJgcoj8mOR.css
300 ms
q68gy-v_YMF.js
377 ms
FJmpeSpHpjS.js
393 ms
0wM5s1Khldu.js
299 ms
1bNoFZUdlYZ.js
310 ms
11659409_10153332479300496_1819775221607909509_n.jpg
216 ms
1966783_10151888692335496_1304910571_n.jpg
257 ms
11138646_1392425751083959_290760066182476168_n.jpg
343 ms
3897_10154075779374756_8636109709582302920_n.jpg
334 ms
12814714_180842928960912_8460047399268897627_n.jpg
491 ms
11059920_112647082418132_5371493403912150362_n.jpg
371 ms
HEyyDkPknAC.png
46 ms
wL6VQj7Ab77.png
46 ms
s7jcwEQH7Sx.png
47 ms
I6-MnjEovm5.js
41 ms
pQrUxxo5oQp.js
82 ms
wizarmy.11alive.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.
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
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
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
wizarmy.11alive.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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
wizarmy.11alive.com SEO score
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 Wizarmy.11alive.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 Wizarmy.11alive.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.
wizarmy.11alive.com
Open Graph description is not detected on the main page of Wiz Army 11 Alive. 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: