1.2 sec in total
96 ms
658 ms
467 ms
Click here to check amazing Topup content. Otherwise, check out these important facts you probably never knew about topup.in
International Recharge for mobiles. Send top up to cell phones back home. Fast, instant & secure. Recharge online & safe payment.
Visit topup.inWe analyzed Topup.in page load time and found that the first response time was 96 ms and then it took 1.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.
topup.in performance score
name
value
score
weighting
Value3.3 s
41/100
10%
Value4.5 s
36/100
25%
Value3.3 s
91/100
10%
Value1,040 ms
26/100
30%
Value0.005
100/100
15%
Value9.8 s
28/100
10%
96 ms
177 ms
53 ms
68 ms
22 ms
Our browser made a total of 70 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Topup.in, 56% (39 requests) were made to Topup.com and 23% (16 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (211 ms) relates to the external source Cdn.userway.org.
Page size can be reduced by 198.3 kB (50%)
397.6 kB
199.3 kB
In fact, the total size of Topup.in main page is 397.6 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. 55% of websites need less resources to load. HTML takes 249.4 kB which makes up the majority of the site volume.
Potential reduce by 196.7 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 26.9 kB, which is 11% 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 196.7 kB or 79% of the original size.
Potential reduce by 152 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. Topup images are well optimized though.
Potential reduce by 868 B
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 547 B
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. Topup.in has all CSS files already compressed.
Number of requests can be reduced by 32 (65%)
49
17
The browser has sent 49 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 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 22 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
topup.in
96 ms
topup.com
177 ms
css
53 ms
wtz1ddk.css
68 ms
bootstrap.min.css
22 ms
store_v4.min.css
32 ms
product_mobile_recharge.min.css
35 ms
product_travel_sim.min.css
36 ms
glide.min.css
32 ms
send_page.min.css
34 ms
ada.min.css
33 ms
help_widget.min.css
50 ms
jquery.min.js
49 ms
popper.min.js
58 ms
bootstrap.min.js
65 ms
jquery.validate.min.js
69 ms
validate.min.js
52 ms
glide.min.js
55 ms
mobile_recharge_v4.min.js
52 ms
hero_mobile_recharge_v4.min.js
57 ms
auto-complete.js
48 ms
mr_offer_fragment_carousel.min.js
56 ms
reviews_trustpilot.min.js
63 ms
notifications.min.js
85 ms
ada.min.js
85 ms
store.min.js
85 ms
common.min.js
89 ms
common_events.min.js
85 ms
login_register.min.js
84 ms
reporting.min.js
179 ms
service_worker.min.js
180 ms
form_validator.min.js
180 ms
script-tag.js
49 ms
p.css
28 ms
wheel_right_wh.svg
211 ms
logo.svg
35 ms
homepage_hero_desktop@2x.webp
35 ms
zamani.jpg
35 ms
smartfren.jpg
35 ms
digicel.jpg
38 ms
gtt.jpg
36 ms
tigo.jpg
38 ms
ethiotelecom.jpg
38 ms
orange.jpg
38 ms
cubacel.jpg
37 ms
nauta.jpg
38 ms
star_4.svg
54 ms
star_5.svg
55 ms
Icon-search.svg
54 ms
o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyD9A-9a6VTYyWtZ7rE.woff
41 ms
o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyD9A-9U6VTYyWtZ7rGW9w.woff
58 ms
o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyD9A-9V6VTYyWtZ7rGW9w.woff
70 ms
o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyD9A-9Z6VTYyWtZ7rGW9w.woff
71 ms
o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyD9A-9W6VTYyWtZ7rGW9w.woff
70 ms
o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyD9A-9b6VTYyWtZ7rGW9w.woff
72 ms
o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyD9A-9e6VTYyWtZ7rGW9w.woff
70 ms
o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyD9A-9X6VTYyWtZ7rGW9w.woff
71 ms
o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyAaBO9a6VTYyWtZ7rE.woff
71 ms
o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyAaBO9U6VTYyWtZ7rGW9w.woff
73 ms
o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyAaBO9V6VTYyWtZ7rGW9w.woff
72 ms
o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyAaBO9Z6VTYyWtZ7rGW9w.woff
72 ms
o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyAaBO9W6VTYyWtZ7rGW9w.woff
72 ms
o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyAaBO9b6VTYyWtZ7rGW9w.woff
73 ms
o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyAaBO9e6VTYyWtZ7rGW9w.woff
73 ms
o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyAaBO9X6VTYyWtZ7rGW9w.woff
73 ms
gtm.js
133 ms
d
21 ms
d
33 ms
d
32 ms
flags_v4.min.css
19 ms
topup.in 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.
topup.in 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
topup.in 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 Topup.in 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 Topup.in 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.
topup.in
Open Graph data is detected on the main page of Topup. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: