3.3 sec in total
136 ms
2.3 sec
805 ms
Welcome to crayzbees.com homepage info - get ready to check Crayzbees best content for United States right away, or after learning these important things about crayzbees.com
Visit crayzbees.comWe analyzed Crayzbees.com page load time and found that the first response time was 136 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
crayzbees.com performance score
name
value
score
weighting
Value4.3 s
19/100
10%
Value6.3 s
10/100
25%
Value9.1 s
14/100
10%
Value20 ms
100/100
30%
Value0.027
100/100
15%
Value10.1 s
26/100
10%
136 ms
26 ms
25 ms
49 ms
43 ms
Our browser made a total of 280 requests to load all elements on the main page. We found that 14% of them (39 requests) were addressed to the original Crayzbees.com, 7% (20 requests) were made to S3.amazonaws.com and 4% (11 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (608 ms) relates to the external source Staticxx.facebook.com.
Page size can be reduced by 2.1 MB (58%)
3.6 MB
1.5 MB
In fact, the total size of Crayzbees.com main page is 3.6 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 2.1 MB which makes up the majority of the site volume.
Potential reduce by 282.2 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 282.2 kB or 86% of the original size.
Potential reduce by 174.2 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. Obviously, Crayzbees needs image optimization as it can save up to 174.2 kB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 1.5 MB
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 1.5 MB or 69% of the original size.
Potential reduce by 138.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. Crayzbees.com needs all CSS files to be minified and compressed as it can save up to 138.9 kB or 83% of the original size.
Number of requests can be reduced by 163 (66%)
247
84
The browser has sent 247 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Crayzbees. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 78 to 1 for JavaScripts and from 27 to 1 for CSS and as a result speed up the page load time.
crayzbees.com
136 ms
shareaholic.js
26 ms
wp-emoji-release.min.js
25 ms
ppibfi_pinterest.css
49 ms
style.css
43 ms
style.css
49 ms
css
36 ms
style.css
50 ms
jetpack.css
53 ms
style.css
52 ms
jquery.js
84 ms
jquery-migrate.min.js
67 ms
ppibfi_pinterest.js
67 ms
script.js
81 ms
show_ads.js
11 ms
windo.js
191 ms
jquery-1.11.3.min.js
46 ms
fyitrack_lg.js
459 ms
nmedianet.js
144 ms
show_ads.js
18 ms
q
18 ms
linqia.js
34 ms
254 ms
infolinks_main.js
66 ms
infolinks_main.js
67 ms
devicepx-jetpack.js
16 ms
gprofiles.js
63 ms
wpgroho.js
76 ms
hoverIntent.min.js
75 ms
superfish.min.js
139 ms
superfish.args.min.js
138 ms
superfish.compat.min.js
139 ms
wp-embed.min.js
140 ms
e-201611.js
16 ms
19196c3d16c3b86cd5ea1d451070b5fa.json
55 ms
css
19 ms
css
28 ms
css
38 ms
css
31 ms
css
36 ms
css
37 ms
css
32 ms
css
39 ms
analytics.js
47 ms
ca-pub-1294882056237954.js
104 ms
zrt_lookup.html
154 ms
show_ads_impl.js
99 ms
impression.track
309 ms
19147054.gif
167 ms
linqia_badge.png
76 ms
type_1.png
166 ms
blogger-badge-150.jpg
165 ms
referrals-125x125-retina.png
307 ms
square-button.jpg
165 ms
badge_black_100.png
77 ms
11880373_1068500316493790_3476459482807107214_n.jpg
75 ms
cropped-143958381396242.jpg
306 ms
style.css
118 ms
1..4-1-150x150.jpg
120 ms
i1..8.3bo-150x150.jpg
120 ms
57j-150x150.jpg
76 ms
57-1-150x150.jpg
118 ms
3-150x150.jpg
120 ms
5712-150x150.jpg
160 ms
1..8.3bHH-150x150.png
266 ms
k-1-150x150.jpg
159 ms
1..8-150x150.jpg
159 ms
1..811-150x150.jpg
159 ms
twitter.png
298 ms
facebook.png
295 ms
googleplus.png
296 ms
pinterest.png
296 ms
feed.png
370 ms
143958381396242-1.gif
545 ms
1439583813962422.gif
380 ms
close.png
370 ms
Snugglebear+new.png
307 ms
fyiblogviews.aspx
301 ms
collect
112 ms
linqia_badge.png
249 ms
shrMain.min.js
85 ms
IhBhtOi02NLuvxWW4RuNVg.ttf
220 ms
cNycqCSU8dNAVKEAWPvbqw.ttf
246 ms
dnU3R-5A_43y5bIyLztPsS3USBnSvpkopQaUR-2r7iU.ttf
276 ms
w_BNdJvVZDRmqy5aSfB2kQ.ttf
275 ms
Y_TKV6o8WovbUd3m_X9aAA.ttf
276 ms
ads
343 ms
osd.js
150 ms
bd9c9499c074.png
182 ms
313a8d6433e3.png
199 ms
ads
321 ms
ads
404 ms
Final-Influencer-badge.svg
296 ms
ads
393 ms
type_1.png
416 ms
jquery.min.js
183 ms
300x250.gif
257 ms
01.png
58 ms
bldscr_ron_lg
53 ms
px.gif
104 ms
px.gif
39 ms
bping.php
32 ms
jstag
35 ms
rtbspub
201 ms
fcmdynet.js
227 ms
gpt.js
23 ms
checksync.php
96 ms
flash_async.js
66 ms
pubads_impl_82.js
66 ms
abp.gif
60 ms
abp.gif
105 ms
acj
269 ms
abg.js
137 ms
usermatch
118 ms
pageview.gif
42 ms
bldscr_ron_lg;vB&cb=1458484843270
73 ms
dvtp_src.js
45 ms
container.html
38 ms
bldscr_ron_lg;vSop&cb=1458484843270
74 ms
bldscr_ron_lg;pv&cb=1458484843270
73 ms
vglnk.js
38 ms
partners.js
139 ms
usermatch
41 ms
type_1.png
135 ms
mediamain.html
516 ms
bg-gradient-1.gif
146 ms
dvtp_src_internal26.js
31 ms
savy_header.png
107 ms
aff_i
115 ms
EM_SavvyShopperWidget;sz=300x250;aff_id=9290;ord=
118 ms
EM_SavvyShopperWidget;sz=320x50;aff_id=9290;ord=
117 ms
EM_SavvyShopperWidget;sz=11x11;aff_id=9290;ord=
117 ms
ad_choices_icon.png
27 ms
aff_i
113 ms
csync.php
168 ms
gr
100 ms
Vu62a8AoJYMAATZZDuoAAAFq%26952
111 ms
ca
123 ms
ecsync.php
106 ms
pixel.htm
105 ms
pixel.gif
82 ms
pixel.gif
82 ms
t2tv7.html
100 ms
visit.js
89 ms
rum
388 ms
pixel
140 ms
log.php
33 ms
ddc.htm
56 ms
1554788652794219898
24 ms
lidar.js
24 ms
sholic.js
129 ms
usermatch
351 ms
beacon.js
47 ms
cms-sh2c.html
116 ms
getad
158 ms
json
58 ms
linqia_badge.png
43 ms
0aa095947f57
45 ms
referrals-125x125-retina.png
44 ms
rum
82 ms
crum
74 ms
rum
97 ms
crum
68 ms
inj_tf.css
86 ms
299 ms
307 ms
linqia_badge.png
10 ms
avs5639.js
7 ms
event.gif
57 ms
event.jpg
31 ms
m
218 ms
ping_match.gif
49 ms
eexelate.js
207 ms
234 ms
sdk.js
429 ms
user_sync.html
207 ms
usersyncup-an.html
197 ms
ice.js
208 ms
widgets.js
203 ms
2964
181 ms
rud
163 ms
lbxTrack.js
270 ms
windo.css
70 ms
iframe.html
228 ms
socket.io-1.2.1.js
70 ms
trackrun.aspx
266 ms
hovercard.css
214 ms
services.css
222 ms
crum
190 ms
pixel
188 ms
i.gif
532 ms
pixel
221 ms
showad.js
206 ms
rs
210 ms
amznassocview.js
303 ms
q
180 ms
q
240 ms
q
240 ms
q
262 ms
g.gif
259 ms
ep
173 ms
b1_D09100_F2D729.png
170 ms
tf.html
169 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
459 ms
overlay.png
118 ms
overlay2.png
142 ms
us.png
141 ms
ep
280 ms
crum
112 ms
css
110 ms
vendor.css
89 ms
main.css
111 ms
modernizr.js
109 ms
vendor.js
182 ms
main.js
109 ms
side-banner-2.jpg
123 ms
ping
213 ms
match-result
325 ms
PugMaster
213 ms
dc.js
217 ms
event.gif
120 ms
lbxTrack388.js
125 ms
380 ms
xd_arbiter.php
307 ms
xd_arbiter.php
608 ms
72 ms
walmart-logo.png
224 ms
WMT-play-button.png
224 ms
intel-logo-blue.png
57 ms
product-1.png
56 ms
product-2.png
56 ms
product-3.png
211 ms
intel-logo-white.png
223 ms
css
132 ms
202 ms
crum
191 ms
crum
291 ms
cfcm.ashx
59 ms
rum
329 ms
53 ms
%7B%22adViewability%22:[%7B%22above_the_fold%22:%20false,%20%22topPos%22:%204.392380952380952,%20%22leftPos%22:%200.6172619047619048%7D]%7D&cb=6347516
92 ms
ClearSans-Regular.ttf
170 ms
s_lbx_code.js
128 ms
pixel
133 ms
Pug
147 ms
usersync.aspx
201 ms
search-widget-sprite.png
121 ms
loader._V1391215615_.gif
88 ms
rum
192 ms
pixel
112 ms
__utm.gif
50 ms
domains
147 ms
ClearSans-Bold.ttf
188 ms
ads
430 ms
net.php
21 ms
Pug
103 ms
Pug
100 ms
Pug
101 ms
generic
33 ms
pixel
100 ms
syndication
185 ms
628048058530410496
264 ms
cm
121 ms
Pug
117 ms
Pug
115 ms
rum
116 ms
Pug
47 ms
xrefid.xgi
21 ms
pixel.gif
45 ms
s43688067696057
22 ms
pixel.gif
111 ms
generic
9 ms
xrefid.xgi
15 ms
Pug
62 ms
ermcm
67 ms
crum
88 ms
pxj
13 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
32 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
103 ms
jstag
52 ms
crayzbees.com 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
Form elements do not have associated labels
Links do not have a discernible name
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
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
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.
crayzbees.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
crayzbees.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
ZH
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Crayzbees.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and it does not match the claimed English language. Our system also found out that Crayzbees.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.
crayzbees.com
Open Graph data is detected on the main page of Crayzbees. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: