16.8 sec in total
62 ms
16.2 sec
545 ms
Welcome to welliam.mobi homepage info - get ready to check Welliam best content right away, or after learning these important things about welliam.mobi
Your complete Web, Mobile, E-Commerce and Digital Marketing agency in Umhlanga Rocks, South Africa. We specialise in true mobile responsive websites, e-commerce. lead generation and online marketing
Visit welliam.mobiWe analyzed Welliam.mobi page load time and found that the first response time was 62 ms and then it took 16.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
welliam.mobi performance score
name
value
score
weighting
Value5.0 s
10/100
10%
Value15.9 s
0/100
25%
Value9.4 s
12/100
10%
Value2,180 ms
6/100
30%
Value0.747
6/100
15%
Value13.3 s
12/100
10%
62 ms
64 ms
56 ms
93 ms
91 ms
Our browser made a total of 89 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Welliam.mobi, 42% (37 requests) were made to Storage.mobilebuilder.net and 35% (31 requests) were made to Files.mobilebuilder.net. The less responsive or slowest element that took the longest time to load (15.8 sec) relates to the external source Static.whatshelp.io.
Page size can be reduced by 665.0 kB (26%)
2.5 MB
1.9 MB
In fact, the total size of Welliam.mobi main page is 2.5 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. 70% of websites need less resources to load. Images take 2.3 MB which makes up the majority of the site volume.
Potential reduce by 46.5 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. This page needs HTML code to be minified as it can gain 18.3 kB, which is 34% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 46.5 kB or 85% of the original size.
Potential reduce by 599.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. Obviously, Welliam needs image optimization as it can save up to 599.0 kB or 26% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 12.3 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. This website has mostly compressed JavaScripts.
Potential reduce by 7.2 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. Welliam.mobi needs all CSS files to be minified and compressed as it can save up to 7.2 kB or 19% of the original size.
Number of requests can be reduced by 37 (44%)
84
47
The browser has sent 84 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Welliam. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 25 to 1 for CSS and as a result speed up the page load time.
welliam.mobi
62 ms
www.bluezonemedia.mobi
64 ms
www.bluezonemedia.mobi
56 ms
styles.css
93 ms
styles-ltr.css
91 ms
animate.min.css
104 ms
font-awesome.min.css
88 ms
widgets.js
86 ms
jquery-1.10.0.min.js
101 ms
app.l10n.js.ashx
10 ms
modernizr-2.8.3.min.js
97 ms
jquery.vide.min.js
97 ms
jquery.scrollTo.min.js
98 ms
jquery.lightbox-0.5.css
99 ms
jquery.lightbox-0.5.min.js
99 ms
flexslider.css
99 ms
jquery.flexslider.min.js
98 ms
jquery-ui-1.10.4.min.js
100 ms
jquery.ui.all.css
99 ms
app.main.js
189 ms
api.js
189 ms
CustomFonts.ashx
62 ms
PageStyles.ashx
82 ms
jquery.ui.base.css
3 ms
jquery.ui.theme.css
9 ms
jquery.ui.core.css
8 ms
jquery.ui.accordion.css
8 ms
jquery.ui.autocomplete.css
8 ms
jquery.ui.button.css
9 ms
jquery.ui.datepicker.css
9 ms
jquery.ui.dialog.css
10 ms
jquery.ui.menu.css
11 ms
jquery.ui.progressbar.css
11 ms
jquery.ui.resizable.css
12 ms
jquery.ui.selectable.css
13 ms
jquery.ui.slider.css
12 ms
jquery.ui.spinner.css
13 ms
jquery.ui.tabs.css
14 ms
jquery.ui.tooltip.css
14 ms
init.js
15798 ms
f9e04dc1-3c81-48c9-98ea-4025c5792821.png
203 ms
like.php
305 ms
visitstatistic.ashx
197 ms
widget_iframe.7dae38096d06923d683a2a807172322a.html
123 ms
email.png
136 ms
dropdown_c1_preview.png
65 ms
35fd79c2-0e2e-40f1-bde0-68d25d8552ce.png
65 ms
70fa9559-84d4-4d92-a763-d988ed2e00d6.jpg
146 ms
4c737773-44c1-4812-a123-f7423438e714.png
142 ms
6cf7992f-d177-40de-8028-87ccc234e409.png
136 ms
be16b9d4-5daa-4b2e-92fd-5096bd1f4277.png
137 ms
5ed99fa4-7585-492b-af19-03416ebdc519.png
152 ms
5af2d467-7f66-4121-aab4-07722fe6187b.png
166 ms
464fd566-9458-47d4-9f0e-e23c7c612576.png
215 ms
e07c7382-e198-47a2-ad89-afdf3d4f6521.png
209 ms
dd564307-a27b-4269-bc70-8caec5cd083d.png
208 ms
ca2afb3f-059a-4b3e-a380-4201ea6f60bf.png
210 ms
f10219ad-3778-45de-8750-73993d1e1b3b.jpg
211 ms
c7ce9d19-5074-497b-a41f-137fc6ab8648.png
254 ms
5645a5dc-4170-4b1c-907e-55251dd9a257.png
253 ms
9d8b2f8b-05c5-4251-81e3-6cab7cbca814.png
258 ms
9a7fbbe9-7317-4760-bc18-4869fa27a900.png
333 ms
ad0c7e34-a4c0-4974-b667-7a55b163df1d.png
255 ms
f8d3a41c-df40-4d87-bacf-aef9f03ba9fd.png
265 ms
5a2bcceb-1484-4a41-a1af-f7ba12d975eb.png
254 ms
1a9b884d-33af-447c-ae5b-e95ce181e800.png
313 ms
bda78205-c845-4cf6-9050-0395b47afd87.png
296 ms
f826c3c5-b2e6-44a2-b226-6363b2c4ce3d.png
312 ms
ae71f8cc-a547-4238-b39a-2f815401b18c.png
291 ms
9be4ad0a-4a77-4f03-8bcf-fd1ede28b770.png
322 ms
893b540a-3dde-47cb-81fe-f50d7a1636b2.png
292 ms
13131228-0ff8-4da8-89b5-7e07b9fa3cc4.png
354 ms
e712dcc7-e972-4108-8904-1f707baf1e69.png
356 ms
c3c15a79-b162-4d28-a61c-67d7f83fde46.png
353 ms
fe4c08d1-eb25-4ef8-a124-56ebf3f9c4d3.png
364 ms
6e8d812f-6c5f-46b8-9fc7-26324c633ebb.png
392 ms
e5e7f3ae-e656-45a9-ae38-121a6bbaaf60.png
393 ms
5b4a0348-376c-4d19-8fe4-b5f25f7c183a.jpg
397 ms
775f8494-1e8d-4ec4-a9f1-1d59eda1e5b8.png
402 ms
c73be41d-ccd3-4dbd-aa6e-62625b2add2e.png
426 ms
recaptcha__en.js
71 ms
MwQ5bhbm2POE2V9BO7h5uGM.woff
438 ms
settings
94 ms
1e37aa21-9a03-46f1-b9ff-14a90c5918ad.png
306 ms
button.d2f864f87f544dc0c11d7d712a191c1f.js
4 ms
embeds
31 ms
tweet_button.7dae38096d06923d683a2a807172322a.en.html
21 ms
9yww5DBsBaL.js
29 ms
FEppCFCt76d.png
19 ms
welliam.mobi accessibility score
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
welliam.mobi 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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
welliam.mobi SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Welliam.mobi 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 Welliam.mobi 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.
welliam.mobi
Open Graph description is not detected on the main page of Welliam. 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: