6.7 sec in total
1.9 sec
4 sec
707 ms
Welcome to mobile.topup.com homepage info - get ready to check Mobile Topup best content for India right away, or after learning these important things about mobile.topup.com
International Recharge for mobiles. Send top up to cell phones back home. Fast, instant & secure. Recharge online & safe payment.
Visit mobile.topup.comWe analyzed Mobile.topup.com page load time and found that the first response time was 1.9 sec and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
mobile.topup.com performance score
name
value
score
weighting
Value3.3 s
41/100
10%
Value4.5 s
37/100
25%
Value3.6 s
87/100
10%
Value1,030 ms
26/100
30%
Value0.003
100/100
15%
Value9.0 s
34/100
10%
1909 ms
128 ms
155 ms
165 ms
176 ms
Our browser made a total of 197 requests to load all elements on the main page. We found that 80% of them (157 requests) were addressed to the original Mobile.topup.com, 8% (16 requests) were made to Topupcom.files.wordpress.com and 3% (6 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Mobile.topup.com.
Page size can be reduced by 337.3 kB (39%)
854.4 kB
517.0 kB
In fact, the total size of Mobile.topup.com main page is 854.4 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 60% of websites need less resources to load. Images take 355.1 kB which makes up the majority of the site volume.
Potential reduce by 108.3 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 108.3 kB or 83% of the original size.
Potential reduce by 1 B
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. Mobile Topup images are well optimized though.
Potential reduce by 46.4 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 46.4 kB or 30% of the original size.
Potential reduce by 182.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. Mobile.topup.com needs all CSS files to be minified and compressed as it can save up to 182.6 kB or 85% of the original size.
Number of requests can be reduced by 29 (16%)
178
149
The browser has sent 178 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mobile Topup. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
mobile.topup.com
1909 ms
css
128 ms
css
155 ms
css
165 ms
css
176 ms
css
173 ms
css
174 ms
bootstrap.css
205 ms
styles-v3.css
139 ms
font-awesome.min.css
89 ms
jquery.min.js
154 ms
bootstrap.min.js
139 ms
wow.min.js
150 ms
ie10-viewport-bug-workaround.js
186 ms
jquery.bxslider2.min.js
188 ms
dv1-scripts.js
189 ms
dv1-slider.css
188 ms
scroll-to-top.js
169 ms
form_validation.js
215 ms
jquery.bootstrap.newsbox.min.js
220 ms
analytics.js
71 ms
conversion.js
182 ms
collect
29 ms
notFound.asp
132 ms
notFound.asp
151 ms
collect
52 ms
ga-audiences
37 ms
fbevents.js
256 ms
flow-logo.png
196 ms
TTckApm.jpg
214 ms
topup_logo2c.png
273 ms
globe-menubg.png
275 ms
us.gif
258 ms
down-arrow.png
273 ms
AF.gif
273 ms
AL.gif
257 ms
DZ.gif
313 ms
AS.gif
314 ms
AO.gif
324 ms
AI.gif
325 ms
AG.gif
312 ms
AR.gif
325 ms
AM.gif
416 ms
AW.gif
404 ms
BH.gif
404 ms
BD.gif
415 ms
BB.gif
416 ms
BY.gif
396 ms
BZ.gif
453 ms
BJ.gif
483 ms
BM.gif
484 ms
BO.gif
470 ms
BR.gif
481 ms
VG.gif
469 ms
BF.gif
514 ms
BI.gif
516 ms
KH.gif
515 ms
KY.gif
545 ms
CF.gif
545 ms
CL.gif
538 ms
CN.gif
547 ms
CO.gif
557 ms
CG.gif
558 ms
CD.gif
592 ms
CR.gif
593 ms
image00125.png
182 ms
gtt.png
181 ms
image00128.png
183 ms
claro.png
183 ms
image0017.png
183 ms
natcom-haiti.jpg
184 ms
airtel.png
184 ms
ga.js
77 ms
291 ms
CU.gif
426 ms
flow-logo.png
242 ms
image00125.png
240 ms
gtt.png
224 ms
claro.png
223 ms
image00128.png
223 ms
image0017.png
235 ms
natcom-haiti.jpg
236 ms
airtel.png
234 ms
toadOcfmlt9b38dHJxOBGMw1o1eFRj7wYC6JbISqOjY.ttf
247 ms
ODelI1aHBYDBqgeIAH2zlNzbP97U9sKh0jjxbPbfOKg.ttf
284 ms
fontawesome-webfont.woff
154 ms
b9QBgL0iMZfDSpmcXcE8nL3QFSXBldIn45k5A7iXhnc.ttf
316 ms
Zd2E9abXLFGSr9G3YK2MsDR-eWpsHSw83BRsAQElGgc.ttf
317 ms
253 ms
glyphicons-halflings-regular.woff
356 ms
CY.gif
351 ms
DM.gif
353 ms
DO.gif
384 ms
EC.gif
388 ms
SV.gif
386 ms
ET.gif
352 ms
FJ.gif
365 ms
FR.gif
368 ms
GF.gif
386 ms
GA.gif
394 ms
GM.gif
394 ms
GE.gif
322 ms
DE.gif
327 ms
GD.gif
323 ms
GT.gif
352 ms
GN.gif
360 ms
GW.gif
357 ms
14 ms
GY.gif
311 ms
HT.gif
313 ms
HN.gif
321 ms
IN.gif
340 ms
CI.gif
347 ms
JM.gif
333 ms
KE.gif
318 ms
KW.gif
321 ms
KG.gif
317 ms
LA.gif
331 ms
LR.gif
338 ms
LT.gif
339 ms
MK.gif
328 ms
MG.gif
322 ms
MY.gif
335 ms
ML.gif
332 ms
MQ.gif
335 ms
MX.gif
338 ms
notFound.asp
352 ms
MD.gif
324 ms
MS.gif
337 ms
MZ.gif
334 ms
MM.gif
332 ms
NR.gif
339 ms
NP.gif
336 ms
AN.gif
339 ms
NI.gif
338 ms
NE.gif
336 ms
PA.gif
327 ms
PG.gif
335 ms
PY.gif
333 ms
PE.gif
341 ms
PH.gif
336 ms
PL.gif
332 ms
PR.gif
324 ms
RO.gif
354 ms
RU.gif
352 ms
RW.gif
349 ms
WS.gif
339 ms
SN.gif
332 ms
RS.gif
324 ms
SG.gif
325 ms
SB.gif
337 ms
SO.gif
349 ms
ZA.gif
337 ms
ES.gif
331 ms
LK.gif
321 ms
KN.gif
323 ms
LC.gif
338 ms
VC.gif
351 ms
SD.gif
338 ms
SR.gif
326 ms
SZ.gif
326 ms
TJ.gif
319 ms
TZ.gif
335 ms
TH.gif
336 ms
TG.gif
330 ms
glyphicons-halflings-regular.ttf
377 ms
TO.gif
325 ms
TT.gif
321 ms
TR.gif
337 ms
TC.gif
335 ms
UG.gif
336 ms
UA.gif
328 ms
AE.gif
333 ms
US.gif
338 ms
UY.gif
352 ms
UZ.gif
339 ms
VU.gif
346 ms
YE.gif
322 ms
ZM.gif
329 ms
ZW.gif
315 ms
close_box2.png
328 ms
logos-callingcards.png
334 ms
logos-mobilecaller.png
341 ms
logos-conferencecalls.png
318 ms
logos-interpreter.png
327 ms
logos-corporatecalling.png
344 ms
arrow-left.png
344 ms
map-gray.png
500 ms
dv1-carrier_logos7.png
389 ms
dv1-carrier_logos6.png
422 ms
dv1-carrier_logos4.png
432 ms
dv1-carrier_logos3.png
400 ms
dv1-carrier_logos1.png
450 ms
dv1-carrier_logos5.png
439 ms
dv1-carrier_logos2.png
477 ms
bg-building1.jpg
527 ms
card.png
436 ms
mobile.topup.com 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
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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
mobile.topup.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
Page has valid source maps
mobile.topup.com SEO score
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mobile.topup.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 Mobile.topup.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.
mobile.topup.com
Open Graph description is not detected on the main page of Mobile Topup. 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: