4.3 sec in total
709 ms
2.6 sec
956 ms
Welcome to awesometoyz.com homepage info - get ready to check Awesometoyz best content for United States right away, or after learning these important things about awesometoyz.com
Visit awesometoyz.comWe analyzed Awesometoyz.com page load time and found that the first response time was 709 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.
awesometoyz.com performance score
name
value
score
weighting
Value3.5 s
33/100
10%
Value4.0 s
51/100
25%
Value3.5 s
88/100
10%
Value50 ms
100/100
30%
Value0.012
100/100
15%
Value4.0 s
88/100
10%
709 ms
256 ms
155 ms
233 ms
303 ms
Our browser made a total of 90 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Awesometoyz.com, 38% (34 requests) were made to Cdn6.bigcommerce.com and 36% (32 requests) were made to Cdn5.bigcommerce.com. The less responsive or slowest element that took the longest time to load (709 ms) belongs to the original domain Awesometoyz.com.
Page size can be reduced by 516.3 kB (41%)
1.3 MB
742.4 kB
In fact, the total size of Awesometoyz.com main page is 1.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. 70% of websites need less resources to load. Images take 591.2 kB which makes up the majority of the site volume.
Potential reduce by 123.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 123.1 kB or 83% of the original size.
Potential reduce by 9.6 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. Awesometoyz images are well optimized though.
Potential reduce by 348.2 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 348.2 kB or 73% of the original size.
Potential reduce by 35.4 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. Awesometoyz.com needs all CSS files to be minified and compressed as it can save up to 35.4 kB or 81% of the original size.
Number of requests can be reduced by 47 (58%)
81
34
The browser has sent 81 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Awesometoyz. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and from 19 to 1 for CSS and as a result speed up the page load time.
awesometoyz.com
709 ms
atrk.js
256 ms
css
155 ms
css
233 ms
css
303 ms
styles.css
153 ms
iselector.css
151 ms
flexslider.css
153 ms
slide-show.css
147 ms
styles-slide-show.css
149 ms
social.css
147 ms
styles.css
276 ms
responsive.css
206 ms
grid.css
206 ms
menu.css
210 ms
theme.css
209 ms
product.attributes.css
274 ms
ui.all.css
273 ms
product.quickview.css
277 ms
imodal.css
275 ms
jquery.min.js
370 ms
menudrop.js
178 ms
iselector.js
172 ms
jquery.flexslider.js
178 ms
viewport.js
179 ms
matchMedia.js
197 ms
common.js
197 ms
jquery.autobox.js
245 ms
init.js
247 ms
jquery.uniform.min.js
251 ms
main.js
252 ms
site.js
268 ms
jquery-ui.min.js
543 ms
jquery.validate.js
264 ms
product.functions.js
362 ms
product.attributes.js
362 ms
quickview.js
360 ms
quickview.initialise.js
356 ms
jquery.form.js
356 ms
imodal.js
354 ms
quicksearch.js
402 ms
bc_pinstrumentation.min.js
376 ms
visitor.js
375 ms
atrk.gif
457 ms
css
77 ms
analytics.js
299 ms
analytics.min.js
172 ms
test.png
568 ms
FUDHvzEKSJww3kCxuiAo2A.ttf
292 ms
0XxGQsSc1g4rdRdjJKZrNC3USBnSvpkopQaUR-2r7iU.ttf
318 ms
beacon_api.js
65 ms
loader.png
241 ms
RSS.gif
240 ms
logo_boy_girl_fireworks_1412002087__81942.png
263 ms
Display_Banner.png
347 ms
Funko_Arrow_Black_Canary_Pop_Vinyl_Figure__87233.1424111968.190.250.jpg
231 ms
IcoRating0.png
229 ms
The_Walking_Dead_Hershel_Pop_Vinyl_Figure_Funko__19681.1405549472.190.250.jpg
244 ms
DC_Comics_The_Riddler_Bendable_Figure_Classic_TV_Series__99578.1424547728.190.250.jpg
246 ms
a2079171466ee700b132a9_l__20461.1404873538.190.250.jpg
248 ms
Peanuts_Sally_Brown_Pop_Vinyl_Figure__70357.1430699248.190.250.jpg
247 ms
Avengers_Age_of_Ultron_Iron_Man_Pop_Vinyl_Bobble_Head_Figure_Funko__03684.1421946594.190.250.jpg
248 ms
Dancing_Groot_POP__76611.1408977643.190.250.jpg
251 ms
IcoRating5.png
251 ms
a207919145250156d48950_m__87028.1404873549.190.250.jpg
268 ms
IcoRating4.png
252 ms
Reverse_Flash_TV_Series_Pop_Vinyl_Figure_Funko__79301.1425338538.190.250.jpg
263 ms
Custom_Display_1__75571.1439568540.190.250.png
292 ms
Funko_Pop_Vinyl_10_Piece_Display__92788.1405650792.190.250.jpg
264 ms
Shaun_of_the_Dead_Ed_Pop_Vinyl_Figure__94216.1441729448.190.250.jpg
265 ms
Shaun_of_the_Dead_Shaun_Pop_Vinyl_Figure__67446.1441729360.190.250.jpg
268 ms
Jungle_Book_King_Louie_Orangutan_Disney_Pop_Vinyl_Figure__61452.1441650774.190.250.jpg
285 ms
Funko_Firefly_Kaylee_Frye_Pop_Vinyl_Figure__69035.1441650582.190.250.jpg
287 ms
Funko_POP_Magic_The_Gathering_Tezzeret__88440.1441417957.190.250.jpg
287 ms
FunKo_POP_TV_X_Files_Fox_Mulder_Toy_Figure__36356.1441417511.190.250.jpg
287 ms
fornax.min.js
216 ms
collect
158 ms
blank.png
122 ms
fontawesome-webfont.woff
171 ms
collect
525 ms
coupon_code1.js
403 ms
nHiQo1BypvYzt95zlPq1TvesZW2xOQ-xsNqO47m55DA.ttf
360 ms
TNtGAwzXtCEY_5hzRlIJNPesZW2xOQ-xsNqO47m55DA.ttf
367 ms
187TYb8ysVvxar86IcDsZ_esZW2xOQ-xsNqO47m55DA.ttf
359 ms
K6ngFdK5haaaRGBV8waDwA.ttf
357 ms
sprite-social-theme.png
315 ms
index.php
319 ms
account_version_check.html
83 ms
coupon_code2.js
36 ms
account_config.html
35 ms
awesometoyz.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.
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
awesometoyz.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
awesometoyz.com SEO score
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 doesn't use legible font sizes
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Awesometoyz.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Awesometoyz.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.
awesometoyz.com
Open Graph description is not detected on the main page of Awesometoyz. 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: