3.4 sec in total
22 ms
3 sec
306 ms
Welcome to crazysms.in homepage info - get ready to check Crazysms best content for India right away, or after learning these important things about crazysms.in
crazysms.in 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, crazysms.in has it all. We hope you find wha...
Visit crazysms.inWe analyzed Crazysms.in page load time and found that the first response time was 22 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
crazysms.in performance score
name
value
score
weighting
Value5.3 s
7/100
10%
Value5.4 s
21/100
25%
Value11.1 s
5/100
10%
Value530 ms
56/100
30%
Value0.181
67/100
15%
Value10.5 s
23/100
10%
22 ms
615 ms
87 ms
243 ms
251 ms
Our browser made a total of 87 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Crazysms.in, 17% (15 requests) were made to Apis.google.com and 15% (13 requests) were made to Spicysms.in. The less responsive or slowest element that took the longest time to load (615 ms) relates to the external source Spicysms.in.
Page size can be reduced by 132.9 kB (36%)
370.5 kB
237.7 kB
In fact, the total size of Crazysms.in main page is 370.5 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. 80% 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 184.2 kB which makes up the majority of the site volume.
Potential reduce by 19.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 19.7 kB or 76% of the original size.
Potential reduce by 6.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. Crazysms images are well optimized though.
Potential reduce by 101.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 101.8 kB or 66% of the original size.
Potential reduce by 4.8 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. Crazysms.in needs all CSS files to be minified and compressed as it can save up to 4.8 kB or 74% of the original size.
Number of requests can be reduced by 44 (55%)
80
36
The browser has sent 80 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Crazysms. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 32 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
sHBwqL
22 ms
www.spicysms.in
615 ms
spicysms.css
87 ms
jquery.min.js
243 ms
prototype.js
251 ms
show_ads.js
9 ms
spicysms_logo.png
212 ms
fb.png
186 ms
gplus.png
187 ms
popular.gif
230 ms
new.gif
229 ms
updated.gif
230 ms
gPlay_1.png
231 ms
plusone.js
53 ms
zrt_lookup.html
31 ms
show_ads_impl.js
71 ms
cb=gapi.loaded_0
115 ms
cb=gapi.loaded_1
112 ms
fastbutton
145 ms
ads
225 ms
arrow1.png
135 ms
osd.js
157 ms
cb=gapi.loaded_0
131 ms
cb=gapi.loaded_1
137 ms
postmessageRelay
139 ms
cb=gapi.loaded_2
79 ms
page
321 ms
ads
258 ms
input_bg.png
150 ms
ads
265 ms
likebox.php
499 ms
m_js_controller.js
43 ms
abg.js
84 ms
3193398744-postmessagerelay.js
52 ms
rpc:shindig_random.js
60 ms
favicon
153 ms
googlelogo_color_112x36dp.png
147 ms
nessie_icon_tiamat_white.png
64 ms
cb=gapi.loaded_0
61 ms
s
68 ms
x_button_blue2.png
49 ms
10958725625642598462
71 ms
rs=AGLTcCPjtRAiXMFLnGXB_RDWfN_DXhO_2A
45 ms
rs=AGLTcCPeW_yxohM6d2vzOu9_v18SNdO9Aw
67 ms
rs=AGLTcCNyaaduUvqXSD4CReLtqUtlnUcqnQ
126 ms
7250037180030814912
115 ms
Lrq7Jibxdtv2QOPyDSqncpDfQFNs3PE6SoUrUNh2GTU.js
195 ms
photo.jpg
235 ms
spn.jpg
228 ms
rs=AGLTcCNyaaduUvqXSD4CReLtqUtlnUcqnQ
49 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
72 ms
dtpHsbgPEm2lVWciJZ0P-A.ttf
164 ms
bdHGHleUa-ndQCOrdpfxfw.ttf
183 ms
McLpmVM3wCm.css
49 ms
VH4VPudaxfN.css
137 ms
Czh0gDTFcBt.css
146 ms
hhn-1r1gAPt.css
165 ms
q68gy-v_YMF.js
146 ms
FJmpeSpHpjS.js
197 ms
0wM5s1Khldu.js
145 ms
1bNoFZUdlYZ.js
158 ms
njO1TPvGzoR.js
228 ms
1QuX41zDRrx.js
230 ms
Oagsvfb4VWi.js
233 ms
LTv6ZK-5zxz.js
254 ms
1FCa-btixu2.js
229 ms
rs=AGLTcCNyaaduUvqXSD4CReLtqUtlnUcqnQ
23 ms
11822517_850923068337427_6872642312971795324_n.jpg
155 ms
11891166_860109430752124_4765018067639208490_n.jpg
147 ms
995373_463884177147328_2272023801786376889_n.jpg
160 ms
10649931_788826447889231_4937881246293638935_n.jpg
189 ms
12654493_1537954769866393_8027120733689257692_n.jpg
159 ms
1917820_851481034981260_5605922336349456134_n.jpg
215 ms
2540_176505236071377_8557006286594037639_n.jpg
159 ms
3423_962363603860039_903758576370481036_n.jpg
160 ms
993564_962251580537908_7899526251811562498_n.jpg
216 ms
1919355_962231793873220_9205466876853276861_n.jpg
228 ms
1001125_962213663875033_4280789500711361543_n.jpg
174 ms
1935855_960521264044273_8899033398972866126_n.jpg
192 ms
wL6VQj7Ab77.png
114 ms
s7jcwEQH7Sx.png
122 ms
QDwYpIaRyfG.png
131 ms
sSwLTfB7PfP.png
132 ms
K00K-UgnsKu.png
131 ms
I6-MnjEovm5.js
7 ms
pQrUxxo5oQp.js
15 ms
ui
32 ms
crazysms.in accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
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
crazysms.in best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
crazysms.in 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 uses legible font sizes
Tap targets are not sized appropriately
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Crazysms.in can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Crazysms.in 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.
crazysms.in
Open Graph description is not detected on the main page of Crazysms. 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: