5.4 sec in total
1.1 sec
3.3 sec
967 ms
Welcome to xsmell.com homepage info - get ready to check Xsmell best content right away, or after learning these important things about xsmell.com
This website is for sale! xsmell.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, xsmell.com has it a...
Visit xsmell.comWe analyzed Xsmell.com page load time and found that the first response time was 1.1 sec and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
xsmell.com performance score
name
value
score
weighting
Value0.8 s
100/100
10%
Value0.8 s
100/100
25%
Value1.4 s
100/100
10%
Value60 ms
100/100
30%
Value0.197
62/100
15%
Value2.9 s
96/100
10%
1051 ms
168 ms
205 ms
244 ms
320 ms
Our browser made a total of 96 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Xsmell.com, 22% (21 requests) were made to Scontent.xx.fbcdn.net and 2% (2 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Scontent.xx.fbcdn.net.
Page size can be reduced by 222.6 kB (34%)
664.3 kB
441.7 kB
In fact, the total size of Xsmell.com main page is 664.3 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 75% 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. Images take 388.8 kB which makes up the majority of the site volume.
Potential reduce by 218.7 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 218.7 kB or 79% of the original size.
Potential reduce by 3.8 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. Xsmell images are well optimized though.
Number of requests can be reduced by 57 (60%)
95
38
The browser has sent 95 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Xsmell. 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 21 to 1 for CSS and as a result speed up the page load time.
xsmell
1051 ms
bzR9dIGvt6h.css
168 ms
kTub4bakEmM.css
205 ms
kyEKgjk51ZE.css
244 ms
gHc7iBOpJF2.css
320 ms
b_nc0vjtAUF.css
291 ms
jri1RqGgcfE.css
336 ms
sFTVm4Wm5AN.css
295 ms
-XVHFgfK3st.css
293 ms
avmpRmLcppA.css
297 ms
ZeuPykSxSED.css
368 ms
v_An6I20hBD.css
344 ms
CZR2Y_i2ZXq.css
345 ms
RhKYB95vxw7.css
347 ms
LEfmrcqFla1.css
351 ms
csYOrJqCGrF.css
362 ms
19A3ofCNcSq.css
376 ms
o-mG5yFm_Th.css
375 ms
N-k91nHCZS2.css
411 ms
hEitKOs4yx9.css
389 ms
5ngtluj4kLT.css
402 ms
A9Xo2v4l1Hp.css
406 ms
FAHeNGXgPup.js
451 ms
event
238 ms
10473339_253457684778131_1393123959756471057_o.jpg
494 ms
static_map.php
486 ms
10501642_253353698121863_3450467968111067015_n.jpg
736 ms
12140583_10153732124478746_1859356308649603806_n.jpg
901 ms
12669433_10207288647267386_1609697539196124020_n.jpg
895 ms
10354686_10150004552801856_220367501106153455_n.jpg
891 ms
12140583_10153732124478746_1859356308649603806_n.jpg
895 ms
10616003_264129137044319_8938150419024130711_n.jpg
895 ms
10526177_254695274654372_303412933815754562_n.jpg
896 ms
10522443_253966911393875_9118972532458520868_n.jpg
1036 ms
10427276_253996674724232_7166526578920356347_n.jpg
1041 ms
10347499_253457684778131_1393123959756471057_n.jpg
1038 ms
10501642_253353698121863_3450467968111067015_n.jpg
1058 ms
10501642_253353698121863_3450467968111067015_n.jpg
1040 ms
10616003_264129137044319_8938150419024130711_n.jpg
1060 ms
10526177_254695274654372_303412933815754562_n.jpg
1189 ms
10522443_253966911393875_9118972532458520868_n.jpg
1061 ms
ZVyMWStefv_.png
205 ms
K00K-UgnsKu.png
217 ms
wL6VQj7Ab77.png
227 ms
-PAXP-deijE.gif
228 ms
ZrLxvLoiUzX.png
228 ms
GsNJNwuI-UM.gif
229 ms
10173492_253427308114502_2080338940_n.jpg
975 ms
LXQaqfwANV7.png
151 ms
geAvKyblz0A.png
176 ms
771IZlQU7KP.png
175 ms
ZYpT1aFajd7.png
173 ms
l5aPruN9xMM.png
173 ms
spacer.gif
95 ms
UHNY_g5mVbr.js
95 ms
FJmpeSpHpjS.js
159 ms
hbybLXHu6w1.js
157 ms
Oagsvfb4VWi.js
251 ms
1bNoFZUdlYZ.js
140 ms
_UYztdBNTjs.js
154 ms
1FCa-btixu2.js
153 ms
7BE0CZr3HTs.js
282 ms
IjqSyiwKeaX.js
279 ms
RTHSWgdzleR.js
279 ms
OZFAYTv-ZUg.js
278 ms
m-2AbGY1fWh.js
287 ms
VfAud2trIQQ.js
284 ms
kvx5eeRG4FE.js
548 ms
Nn19HjwCsOL.js
275 ms
pQrUxxo5oQp.js
423 ms
J0ZuTxeV0vD.js
271 ms
H3EKDTObx05.js
422 ms
bh5z0Gfv2P_.js
422 ms
njEKf1WUXml.js
423 ms
kGXyTJNoi6f.js
422 ms
yXuA_dMgOm6.js
526 ms
1QuX41zDRrx.js
538 ms
yMCR4PoU6B-.js
536 ms
7uWMMev-gdj.js
534 ms
yBzWdmXwoNV.js
500 ms
Wcs1PDXzIEa.js
656 ms
MIunLE9xhJ4.js
650 ms
c05laeT1OPx.js
651 ms
-sVccfRXDIY.js
655 ms
UiJCRDQUmbL.js
647 ms
ZPCmDKlM9R2.js
203 ms
18881_10204081468098613_5646793032136958900_n.jpg
154 ms
10984208_10152730973402861_3547477767679383102_n.jpg
150 ms
11698635_10200696801137727_1431054111604618751_n.jpg
154 ms
1931325_1215022138511125_5340652897402369678_n.jpg
207 ms
aeO1ik7i7-T.png
149 ms
I6-MnjEovm5.js
42 ms
Dppan5o6UJu.js
47 ms
8v2_hdH4Nfm.js
47 ms
-Tr757ZEtMP.js
161 ms
A0qdgknEnD5.js
53 ms
xsmell.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.
xsmell.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
xsmell.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 Xsmell.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 Xsmell.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.
xsmell.com
Open Graph description is not detected on the main page of Xsmell. 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: