6.6 sec in total
672 ms
5.2 sec
678 ms
Welcome to wearebawsome.com homepage info - get ready to check Wearebawsome best content right away, or after learning these important things about wearebawsome.com
wearebawsome.com is your first and best source for all of the information you’re looking for. From general topics to more of what you would expect to find here, wearebawsome.com has it all. We hope yo...
Visit wearebawsome.comWe analyzed Wearebawsome.com page load time and found that the first response time was 672 ms and then it took 5.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
wearebawsome.com performance score
name
value
score
weighting
Value0.8 s
100/100
10%
Value0.8 s
100/100
25%
Value1.8 s
100/100
10%
Value160 ms
93/100
30%
Value0.197
62/100
15%
Value3.1 s
95/100
10%
672 ms
328 ms
226 ms
343 ms
658 ms
Our browser made a total of 111 requests to load all elements on the main page. We found that 68% of them (75 requests) were addressed to the original Wearebawsome.com, 17% (19 requests) were made to Scontent.cdninstagram.com and 4% (4 requests) were made to F.vimeocdn.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Wearebawsome.com.
Page size can be reduced by 726.8 kB (12%)
6.1 MB
5.4 MB
In fact, the total size of Wearebawsome.com main page is 6.1 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 5.3 MB which makes up the majority of the site volume.
Potential reduce by 49.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 9.6 kB, which is 16% 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 49.6 kB or 81% of the original size.
Potential reduce by 57.7 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. Wearebawsome images are well optimized though.
Potential reduce by 326.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 326.2 kB or 67% of the original size.
Potential reduce by 293.3 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. Wearebawsome.com needs all CSS files to be minified and compressed as it can save up to 293.3 kB or 87% of the original size.
Number of requests can be reduced by 14 (14%)
102
88
The browser has sent 102 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wearebawsome. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and as a result speed up the page load time.
wearebawsome.com
672 ms
jquery-1.11.3.min.js
328 ms
style_mobile.css
226 ms
81cdc3312f58a4b3d634cac249f6d3cc.css
343 ms
3ddefa2c74ddbe9f2e5d6ec80794e25c.js
658 ms
analytics.js
46 ms
fbds.js
47 ms
loading.gif
250 ms
wearebawsome.com
584 ms
icons.png
179 ms
bawsome-mobile.png
179 ms
sprite.png
466 ms
h1.jpg
930 ms
h2.jpg
1194 ms
h3.jpg
1217 ms
bawsome_white.png
566 ms
s1.jpg
1220 ms
s2.jpg
1361 ms
s3.jpg
1324 ms
s4.jpg
1286 ms
s5.jpg
1572 ms
s6.jpg
1566 ms
s7.jpg
1627 ms
s8.jpg
1577 ms
s9.jpg
1675 ms
s10.jpg
1997 ms
s11.jpg
2058 ms
s12.jpg
2066 ms
s13.jpg
2093 ms
s14.jpg
2296 ms
s15.jpg
2411 ms
s16.jpg
2368 ms
s17.jpg
2393 ms
preview.png
2260 ms
preview.png
2217 ms
glassesMenu2.png
2345 ms
glassesMenu4.png
2388 ms
glassesMenu3.png
2449 ms
temples_left.png
2468 ms
lens.png
2533 ms
temples_right.png
2534 ms
front.png
2553 ms
temples_left.png
2534 ms
113998916
91 ms
collect
29 ms
41 ms
collect
22 ms
collect
144 ms
player.js
144 ms
player.css
121 ms
ga.js
92 ms
vuid.min.js
137 ms
recent
531 ms
BebasNeueRegular.otf
2526 ms
Oswald-Light.ttf
2472 ms
__utm.gif
30 ms
BebasNeueBold.otf
2444 ms
proxy.html
41 ms
499533090.jpg
82 ms
8846181_60x60.jpg
56 ms
glyphicons-halflings-regular.woff
2209 ms
Oswald.otf
2137 ms
hadrianbold.woff
2111 ms
12599328_1076109185773991_391033104_n.jpg
348 ms
12728574_1512023225772363_1635030775_n.jpg
677 ms
12729453_1646841622247898_715022815_n.jpg
685 ms
12677286_175151022855765_676991863_n.jpg
611 ms
12558953_1060587553980955_1831780851_n.jpg
737 ms
12479257_803926933052181_640233922_n.jpg
686 ms
12552220_792864507484429_1546979655_n.jpg
750 ms
12407413_1506810336287794_107980951_n.jpg
1045 ms
10249361_1750270401871895_1551437411_n.jpg
892 ms
12501726_1034109516631501_321621592_n.jpg
752 ms
12327972_156850751336871_600111946_n.jpg
1477 ms
12353195_601894449961310_1671135789_n.jpg
1237 ms
12317683_100352537002971_11081727_n.jpg
886 ms
12298866_513287238839254_1191824003_n.jpg
899 ms
12298791_531327660360955_694599432_n.jpg
1026 ms
12298817_1523874104592018_1900305102_n.jpg
1044 ms
12298803_854149251368897_2129485230_n.jpg
965 ms
12292718_975577892480881_1448019889_n.jpg
1099 ms
12276736_461175920752821_1481162242_n.jpg
1302 ms
Verdana.woff
2168 ms
temples_right.png
1687 ms
lens.png
1930 ms
front.png
1901 ms
temples_right.png
1733 ms
lens.png
1703 ms
front.png
1766 ms
temples_left.png
1769 ms
temples_left.png
1762 ms
lens.png
1709 ms
front.png
1662 ms
temples_right.png
1712 ms
input_border.png
1335 ms
lens.png
1464 ms
lens.png
1348 ms
lens.png
1465 ms
front.png
1344 ms
lens.png
1408 ms
temples_left.png
1209 ms
temples_right.png
1181 ms
front.png
1271 ms
lens.png
1244 ms
temples_left.png
1349 ms
temples_right.png
1403 ms
front.png
1258 ms
lens.png
1287 ms
temples_left.png
1229 ms
temples_right.png
1246 ms
2 ms
wearebawsome.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
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.
wearebawsome.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Issues were logged in the Issues panel in Chrome Devtools
wearebawsome.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wearebawsome.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 Wearebawsome.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.
wearebawsome.com
Open Graph description is not detected on the main page of Wearebawsome. 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: