4.2 sec in total
555 ms
3.4 sec
251 ms
Click here to check amazing SOMETHING content. Otherwise, check out these important facts you probably never knew about something.org
Visit something.orgWe analyzed Something.org page load time and found that the first response time was 555 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
something.org performance score
name
value
score
weighting
Value4.0 s
24/100
10%
Value5.0 s
27/100
25%
Value4.9 s
65/100
10%
Value550 ms
54/100
30%
Value0.053
98/100
15%
Value7.5 s
47/100
10%
555 ms
264 ms
43 ms
263 ms
288 ms
Our browser made a total of 81 requests to load all elements on the main page. We found that 96% of them (78 requests) were addressed to the original Something.org, 2% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Fma.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Something.org.
Page size can be reduced by 132.2 kB (37%)
354.1 kB
221.9 kB
In fact, the total size of Something.org main page is 354.1 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. 20% of websites need less resources to load. Images take 178.2 kB which makes up the majority of the site volume.
Potential reduce by 20.3 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 20.3 kB or 83% of the original size.
Potential reduce by 18.3 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. SOMETHING images are well optimized though.
Potential reduce by 80.5 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 80.5 kB or 60% of the original size.
Potential reduce by 13.1 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. Something.org needs all CSS files to be minified and compressed as it can save up to 13.1 kB or 76% of the original size.
Number of requests can be reduced by 20 (25%)
79
59
The browser has sent 79 CSS, Javascripts, AJAX and image requests in order to completely render the main page of SOMETHING. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
something.org
555 ms
reset.css
264 ms
text.css
43 ms
960.css
263 ms
style.css
288 ms
thickbox.css
44 ms
jquery-1.4.4.min.js
297 ms
script.js
327 ms
jquery.flow.1.2.min.js
277 ms
jquery.corner.js
987 ms
thickbox.js
324 ms
jcarousellite_1.0.1.js
350 ms
crawler.js
332 ms
bg-page.gif
2112 ms
bg-curve-bottom.gif
71 ms
logo.gif
71 ms
btn-search.gif
69 ms
spotlight.jpg
1037 ms
mp3.gif
108 ms
houseofmedia_scroll.gif
317 ms
dj.gif
318 ms
oxide.gif
108 ms
nameclub.gif
150 ms
arabs.gif
149 ms
newyear.gif
195 ms
osk.gif
194 ms
watani.gif
240 ms
ibiza.gif
483 ms
party.gif
281 ms
jackass.gif
324 ms
liquidtv.gif
357 ms
mail_tv.gif
359 ms
traveltv.gif
369 ms
rock.gif
399 ms
sqwee.gif
404 ms
monsters.gif
412 ms
domain.gif
441 ms
ajmal.gif
445 ms
palette.gif
453 ms
feb.gif
483 ms
impact.gif
487 ms
dgx.gif
495 ms
efx.gif
523 ms
cooperators.gif
524 ms
jogging.gif
532 ms
office_works.gif
536 ms
falcons.gif
563 ms
unaddressed.gif
569 ms
ai.gif
778 ms
axj.gif
515 ms
finaza.gif
543 ms
ga.js
45 ms
nly.gif
512 ms
miki.gif
541 ms
kyr.gif
549 ms
__utm.gif
25 ms
dot-paris.gif
513 ms
inet.gif
540 ms
gotv.gif
505 ms
explore.gif
509 ms
multimedia.gif
493 ms
whynot_src.gif
463 ms
bola.gif
431 ms
twitter_arabs_icon.png
458 ms
arabs_facebook_icon.png
464 ms
logo-redcross.gif
434 ms
logo-unicef.gif
457 ms
logo-habitat.gif
460 ms
bg-curve-top.gif
438 ms
bg-select.gif
450 ms
bg-search.gif
445 ms
bg-seperator.gif
430 ms
bg-home-wrap.gif
432 ms
bg-top-wdgt.jpg
504 ms
arrow.png
418 ms
bg-bottom-wdgt.jpg
430 ms
bullet.png
432 ms
bg-gradient.gif
444 ms
ajax-loader.gif
431 ms
bullet-on.png
660 ms
www.fma.com
348 ms
something.org 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
No form fields have multiple labels
Form elements do not have associated labels
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
something.org 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
something.org 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
EN
HI
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Something.org can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Hindi language. Our system also found out that Something.org 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.
something.org
Open Graph description is not detected on the main page of SOMETHING. 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: