6.1 sec in total
31 ms
5 sec
1.1 sec
Welcome to simonso.org homepage info - get ready to check Simonso best content right away, or after learning these important things about simonso.org
From a new daddy to another. Stuffs to share with new daddys with some tips and tricks when handling our newborn and some highlights of preventing or avoiding the mother tantrum
Visit simonso.orgWe analyzed Simonso.org page load time and found that the first response time was 31 ms and then it took 6.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
simonso.org performance score
name
value
score
weighting
Value3.2 s
42/100
10%
Value19.5 s
0/100
25%
Value13.0 s
2/100
10%
Value3,560 ms
1/100
30%
Value0.173
69/100
15%
Value22.1 s
1/100
10%
31 ms
681 ms
33 ms
83 ms
143 ms
Our browser made a total of 66 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Simonso.org, 11% (7 requests) were made to Blogger.com and 8% (5 requests) were made to Scontent.cdninstagram.com. The less responsive or slowest element that took the longest time to load (3.6 sec) relates to the external source V-b.my.
Page size can be reduced by 298.0 kB (15%)
2.0 MB
1.7 MB
In fact, the total size of Simonso.org main page is 2.0 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. 55% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 72.4 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 72.4 kB or 80% of the original size.
Potential reduce by 21.2 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. Simonso images are well optimized though.
Potential reduce by 123.0 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 123.0 kB or 47% of the original size.
Potential reduce by 81.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. Simonso.org needs all CSS files to be minified and compressed as it can save up to 81.4 kB or 76% of the original size.
Number of requests can be reduced by 33 (54%)
61
28
The browser has sent 61 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Simonso. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
simonso.org
31 ms
www.simonso.org
681 ms
ga.js
33 ms
3645911276-widget_css_bundle.css
83 ms
authorization.css
143 ms
js9.js
54 ms
counter.js
49 ms
counter_xhtml.js
28 ms
3226477086-widgets.js
135 ms
plusone.js
81 ms
__utm.gif
26 ms
counter.asp
5 ms
wrapper.jpg
1780 ms
2015-penang.jpg
126 ms
all.js
162 ms
penang-simonso-2014-2.jpg
251 ms
penang-simonso-2014-4.jpg
323 ms
penang-simonso-2014-5.jpg
216 ms
858571.php
104 ms
icon18_wrench_allbkg.png
104 ms
1139 ms
meter.asp
86 ms
analytics.js
183 ms
mpp.vindicosuite.com
85 ms
t.php
168 ms
cb=gapi.loaded_0
25 ms
bullet.jpg
45 ms
icon18_email.gif
46 ms
icon18_edit_allbkg.gif
48 ms
penang-simonso-2014-1.jpg
226 ms
penang-simonso-2014-3.jpg
191 ms
rss.png
44 ms
header.jpg
3550 ms
content.jpg
1946 ms
footer.jpg
1976 ms
meter.asp
41 ms
0
111 ms
cc_28.js
30 ms
20 ms
xd_arbiter.php
131 ms
xd_arbiter.php
234 ms
30 ms
blank.gif
54 ms
0
12 ms
combined.css
9 ms
smoothDivScroll.css
4 ms
stack_161235.js
49 ms
jquery.min.js
20 ms
analytics.js
21 ms
stackpile.api-bfb5078e74.js
35 ms
12822333_1078413498875451_373422213_n.jpg
89 ms
12816941_110162439379297_1998996047_n.jpg
18 ms
12819063_1749256511960854_710885105_n.jpg
35 ms
12826103_1243910268956776_1212811459_n.jpg
21 ms
12819156_789299541214147_955594499_n.jpg
85 ms
collect
9 ms
collect
53 ms
stackpile.api-bfb5078e74.js
24 ms
nr-885.min.js
15 ms
a53393d12f
54 ms
306752634-lightbox_bundle.css
30 ms
297602417-lbx.js
52 ms
like.php
113 ms
like.php
145 ms
qeKvIRsJabD.js
275 ms
LVx-xkvaJ0b.png
307 ms
simonso.org 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
Image elements do not have [alt] attributes
Links do not have a discernible name
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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.
simonso.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
simonso.org SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Simonso.org 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 Simonso.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.
simonso.org
Open Graph description is not detected on the main page of Simonso. 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: