3.9 sec in total
439 ms
3 sec
441 ms
Welcome to mysmart.community homepage info - get ready to check My Smart best content right away, or after learning these important things about mysmart.community
My Smart Community. Making Smart Communities that are Accessible, Liveable, and Sustainable for All. Smart Community Podcast, Consulting, Speaking
Visit mysmart.communityWe analyzed Mysmart.community page load time and found that the first response time was 439 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
mysmart.community performance score
name
value
score
weighting
Value2.3 s
73/100
10%
Value24.4 s
0/100
25%
Value14.2 s
1/100
10%
Value2,380 ms
5/100
30%
Value0.085
93/100
15%
Value19.3 s
2/100
10%
439 ms
1632 ms
19 ms
24 ms
28 ms
Our browser made a total of 90 requests to load all elements on the main page. We found that 39% of them (35 requests) were addressed to the original Mysmart.community, 36% (32 requests) were made to Fonts.gstatic.com and 20% (18 requests) were made to Webplayer.whooshkaa.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Mysmart.community.
Page size can be reduced by 1.5 MB (39%)
3.8 MB
2.3 MB
In fact, the total size of Mysmart.community main page is 3.8 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. Only a small number of websites need less resources to load. Javascripts take 1.8 MB which makes up the majority of the site volume.
Potential reduce by 228.2 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 228.2 kB or 86% of the original size.
Potential reduce by 100.0 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. My Smart images are well optimized though.
Potential reduce by 1.0 MB
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 1.0 MB or 57% of the original size.
Potential reduce by 111.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. Mysmart.community needs all CSS files to be minified and compressed as it can save up to 111.4 kB or 77% of the original size.
Number of requests can be reduced by 41 (68%)
60
19
The browser has sent 60 CSS, Javascripts, AJAX and image requests in order to completely render the main page of My Smart. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.
mysmart.community
439 ms
mysmart.community
1632 ms
secondline-psb-styles.css
19 ms
style.css
24 ms
jquery.min.js
28 ms
jquery-migrate.min.js
24 ms
js
93 ms
et-core-unified-2541.min.css
34 ms
mediaelementplayer-legacy.min.css
27 ms
wp-mediaelement.min.css
27 ms
modal.min.js
29 ms
scripts.min.js
34 ms
smoothscroll.js
32 ms
es6-promise.auto.min.js
29 ms
api.js
88 ms
recaptcha.js
32 ms
jquery.fitvids.js
32 ms
easypiechart.js
35 ms
salvattore.js
36 ms
common.js
87 ms
mediaelement-and-player.min.js
86 ms
mediaelement-migrate.min.js
36 ms
wp-mediaelement.min.js
37 ms
style.css
17 ms
2701
565 ms
et-divi-dynamic-tb-2976-2541-late.css
10 ms
Community-no-tagline.png
248 ms
Smart-City-Australia.jpg
193 ms
background.header-purple.jpg
192 ms
podcast-headphones.jpg
190 ms
Laptop-Consulting.jpg
258 ms
microphone.jpg
191 ms
about-Zoe-Eather.jpg
193 ms
SCP_E360_2024Updates_SmartCommunityPodcast_BlogTitleImage-768x432.png
254 ms
SCP_E359_SummerSeriesSamAustin_SmartCommunityPodcast_BlogTitleImage-768x432.png
256 ms
SCP_E358_SummerSeriesMichaelWanyama_SmartCommunityPodcast_BlogTitleImage-768x432.png
257 ms
speaking-dark-green.jpg
247 ms
My-Smart-Community-Logo.png
256 ms
font
266 ms
4iCv6KVjbNBYlgoCjC3jvmyI.ttf
293 ms
4iCs6KVjbNBYlgoKcQ7w.woff
304 ms
4iCs6KVjbNBYlgoKcQ7z.ttf
311 ms
4iCv6KVjbNBYlgoC1CzjvmyL.woff
311 ms
4iCv6KVjbNBYlgoC1CzjvmyI.ttf
310 ms
font
390 ms
4iCv6KVjbNBYlgoCxCvjvmyI.ttf
312 ms
recaptcha__en.js
262 ms
4iCp6KVjbNBYlgoKejYHtFyBN4c.woff
192 ms
4iCp6KVjbNBYlgoKejYHtFyBN4Q.ttf
192 ms
4iCu6KVjbNBYlgoKej76l08.woff
192 ms
4iCu6KVjbNBYlgoKej76l0w.ttf
190 ms
4iCp6KVjbNBYlgoKejZftVyBN4c.woff
193 ms
4iCp6KVjbNBYlgoKejZftVyBN4Q.ttf
195 ms
4iCp6KVjbNBYlgoKejZPslyBN4c.woff
194 ms
4iCp6KVjbNBYlgoKejZPslyBN4Q.ttf
197 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDFwmdTo3iQ.woff
193 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDFwmdTo3ig.ttf
195 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDDsmdTo3iQ.woff
197 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDDsmdTo3ig.ttf
196 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDBImdTo3iQ.woff
197 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDBImdTo3ig.ttf
197 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDGUmdTo3iQ.woff
198 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDGUmdTo3ig.ttf
200 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDIkhdTo3iQ.woff
200 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDIkhdTo3ig.ttf
200 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDLshdTo3iQ.woff
200 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDLshdTo3ig.ttf
200 ms
font
259 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDOUhdTo3ig.ttf
200 ms
font
202 ms
XRXI3I6Li01BKofiOc5wtlZ2di8HDDshdTo3ig.ttf
201 ms
normalize.min.css
34 ms
css2
46 ms
app.b04f5f04.css
10 ms
chunk-vendors.33ba588d.js
32 ms
app.55f75d06.js
32 ms
chunk-00fee825.2d8858ff.css
7 ms
chunk-042c52cc.534bef38.css
125 ms
chunk-11409936.2ee25a57.js
34 ms
chunk-59912fde.c01e6e75.css
30 ms
chunk-59912fde.69e72d7e.js
36 ms
chunk-578fef45.499252e1.css
33 ms
chunk-578fef45.8e0ab0b2.js
55 ms
chunk-042c52cc.534bef38.css
49 ms
chunk-042c52cc.1826387a.js
84 ms
chunk-00fee825.2d8858ff.css
34 ms
chunk-00fee825.76fb2625.js
52 ms
chunk-56973e6e.bd12fec8.css
50 ms
chunk-df458ba8.d28e0197.css
60 ms
chunk-df458ba8.674f9850.js
48 ms
mysmart.community 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
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
mysmart.community 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
Page has valid source maps
mysmart.community 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
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mysmart.community 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 Mysmart.community 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.
mysmart.community
Open Graph data is detected on the main page of My Smart. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: