2.9 sec in total
111 ms
2.4 sec
361 ms
Visit fongo.com now to see the best up-to-date Fongo content for Canada and also check out these interesting facts you probably never knew about fongo.com
Founded and based out of Waterloo, Ontario, Fongo provides Canadians with low-cost, personal and small business communication solutions.
Visit fongo.comWe analyzed Fongo.com page load time and found that the first response time was 111 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
fongo.com performance score
name
value
score
weighting
Value3.7 s
30/100
10%
Value9.5 s
0/100
25%
Value7.0 s
33/100
10%
Value740 ms
40/100
30%
Value0.122
84/100
15%
Value9.5 s
30/100
10%
111 ms
114 ms
24 ms
40 ms
42 ms
Our browser made a total of 81 requests to load all elements on the main page. We found that 51% of them (41 requests) were addressed to the original Fongo.com, 10% (8 requests) were made to Apis.google.com and 6% (5 requests) were made to Static.licdn.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Fongo.com.
Page size can be reduced by 1.1 MB (20%)
5.6 MB
4.4 MB
In fact, the total size of Fongo.com main page is 5.6 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 4.1 MB which makes up the majority of the site volume.
Potential reduce by 155.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 155.2 kB or 78% of the original size.
Potential reduce by 88.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. Fongo images are well optimized though.
Potential reduce by 771.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 771.5 kB or 68% of the original size.
Potential reduce by 98.3 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. Fongo.com needs all CSS files to be minified and compressed as it can save up to 98.3 kB or 82% of the original size.
Number of requests can be reduced by 44 (59%)
75
31
The browser has sent 75 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fongo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
fongo.com
111 ms
www.fongo.com
114 ms
base.css
24 ms
layout.css
40 ms
general-styles.css
42 ms
page-styles.css
59 ms
home.css
42 ms
footer.css
44 ms
smartbanner.css
46 ms
lang.en.js
61 ms
ajax_main.js
61 ms
jquery-1.4.2.min.js
120 ms
jquery.blockUI.v2.js
83 ms
main.js
67 ms
smartphone.js
77 ms
smartbanner.js
78 ms
jquery.cycle.js
115 ms
jquery.min.js
145 ms
jquery.cycle.all.latest.js
143 ms
in.js
7 ms
addthis_widget.js
10 ms
ga.js
177 ms
sdk.js
364 ms
widgets.js
157 ms
secureAnonymousFramework
206 ms
platform.js
280 ms
300lo.json
95 ms
header_logo.png
92 ms
banner_1.jpg
677 ms
Mastheads_Home_Header_3.png
1884 ms
banner_2.jpg
574 ms
fongo_conference_banner_eng.jpg
511 ms
banner_4.jpg
792 ms
Mastheads_Home_Header_2.png
1310 ms
gradient-lighter.png
529 ms
home-platform-phones-2014.png
810 ms
home-platform-sprites-new.png
596 ms
gradient-green3.png
618 ms
howitworks-triangle.png
639 ms
talk_canada.png
674 ms
keepnumber-phonebook.png
683 ms
global-social-network-icon.png
747 ms
ios.png
703 ms
android.png
724 ms
blackberry.png
744 ms
fongo_faces_butterfly.png
765 ms
home_phone.png
768 ms
fongo_desktop.png
785 ms
bullet.square.silver.png
787 ms
sh.7c7179124ea24ac6ba46caac.html
50 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
78 ms
__utm.gif
58 ms
xdrpc.html
26 ms
layers.3643cb2e25fb91c29386.js
28 ms
follow_button.6a78875565a912489e9aef879c881358.en.html
82 ms
cb=gapi.loaded_0
59 ms
cb=gapi.loaded_1
86 ms
follow
157 ms
followcompany
75 ms
148 ms
xd_arbiter.php
226 ms
xd_arbiter.php
301 ms
postmessageRelay
59 ms
css
82 ms
anonymoususerspace
29 ms
js
104 ms
css
176 ms
js
181 ms
api.js
156 ms
core:rpc:shindig.random:shindig.sha1.js
165 ms
2536007149-postmessagerelay.js
163 ms
rs=AGLTcCOSgW0-1bB2-oYybIbdW1Z6ktkFEw
26 ms
rs=AGLTcCPhDrHY2vagSjsLFOxeufqSzVU3ow
61 ms
rs=AGLTcCM2Yox_1lk51nTTwbNJK4rlySAFTA
108 ms
pixel
59 ms
jot
166 ms
pixel
101 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
145 ms
dtpHsbgPEm2lVWciJZ0P-A.ttf
160 ms
bdHGHleUa-ndQCOrdpfxfw.ttf
189 ms
sprite_connect_v15.png
29 ms
fongo.com 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
fongo.com 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
fongo.com SEO score
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 Fongo.com 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 Fongo.com 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.
fongo.com
Open Graph data is detected on the main page of Fongo. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: