5.4 sec in total
1.2 sec
3.3 sec
792 ms
Click here to check amazing Twigo content. Otherwise, check out these important facts you probably never knew about twigo.com
Stay in touch by making free and cheap online calls to phones and mobiles with Twigo App. Sign up today and start saving on your international calls.
Visit twigo.comWe analyzed Twigo.com page load time and found that the first response time was 1.2 sec and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
twigo.com performance score
1242 ms
422 ms
178 ms
170 ms
255 ms
Our browser made a total of 65 requests to load all elements on the main page. We found that 71% of them (46 requests) were addressed to the original Twigo.com, 9% (6 requests) were made to Youtube.com and 3% (2 requests) were made to Chat.twigo.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Twigo.com.
Page size can be reduced by 1.1 MB (65%)
1.7 MB
600.0 kB
In fact, the total size of Twigo.com main page is 1.7 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 793.3 kB which makes up the majority of the site volume.
Potential reduce by 38.1 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 13.0 kB, which is 29% 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 38.1 kB or 84% of the original size.
Potential reduce by 19.8 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. Twigo images are well optimized though.
Potential reduce by 608.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 608.3 kB or 77% of the original size.
Potential reduce by 447.6 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. Twigo.com needs all CSS files to be minified and compressed as it can save up to 447.6 kB or 84% of the original size.
Number of requests can be reduced by 38 (63%)
60
22
The browser has sent 60 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Twigo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
twigo.com
1242 ms
bootstrap.min.css
422 ms
bootstrap-theme.min.css
178 ms
jquery.bxslider.css
170 ms
font-awesome.min.css
255 ms
style.css
265 ms
chosen.min.css
332 ms
fb_23.png
333 ms
twit_23.png
339 ms
GB.png
418 ms
BR.png
510 ms
jquery.min.js
1100 ms
jquery-migrate-1.0.0.js
425 ms
jquery-ui.min.js
1089 ms
bootstrap.min.js
866 ms
loader.js
515 ms
jquery.bxslider.js
865 ms
script.js
892 ms
chosen.jquery.min.js
930 ms
1
816 ms
uBslcQyMLSY
129 ms
transpa.png
716 ms
twigo_167_131.png
716 ms
bx1-optimized.jpg
928 ms
bx2-optimized.jpg
958 ms
bx3-optimized.jpg
985 ms
bx4-optimized.jpg
1026 ms
google_play_120_43.png
946 ms
app_store_120_43.png
958 ms
mobiles_106_138.png
1097 ms
swish_106_12.png
1109 ms
CN.png
1114 ms
AO.png
1116 ms
ET.png
1147 ms
FR.png
1188 ms
IN.png
1268 ms
LB.png
1270 ms
PK.png
1276 ms
BD.png
1279 ms
SL.png
1308 ms
NG.png
1351 ms
US.png
1422 ms
bubbles_1200_237.png
1595 ms
icon-sitemap.png
1457 ms
facebook_24.png
1447 ms
tweeter_24.png
1481 ms
analytics.js
7 ms
collect
28 ms
collect
66 ms
www-player.css
18 ms
www-embed-player.js
49 ms
base.js
90 ms
fetch-polyfill.js
45 ms
ga-audiences
391 ms
ad_status.js
187 ms
RLowZH2Xcwtj3dY_yGSeKf8RcILu2Rj3JTO2BWyvP7U.js
105 ms
embed.js
33 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
120 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
120 ms
id
85 ms
Create
106 ms
user_gray_chat.png
163 ms
bx_loader.gif
640 ms
fontawesome-webfont.woff
864 ms
GenerateIT
14 ms
twigo.com SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Twigo.com 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 Twigo.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.
twigo.com
Open Graph description is not detected on the main page of Twigo. 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: