9.7 sec in total
509 ms
8.9 sec
321 ms
Click here to check amazing VIVIFI content for Singapore. Otherwise, check out these important facts you probably never knew about vivifi.me
One Family One Mobile Plan. No usage add-on. Enjoy contract-free shareable mobile plan when you Vivifi your mobile experience.
Visit vivifi.meWe analyzed Vivifi.me page load time and found that the first response time was 509 ms and then it took 9.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
vivifi.me performance score
name
value
score
weighting
Value5.7 s
5/100
10%
Value20.0 s
0/100
25%
Value25.1 s
0/100
10%
Value3,700 ms
1/100
30%
Value0.518
15/100
15%
Value27.6 s
0/100
10%
509 ms
1304 ms
96 ms
33 ms
500 ms
Our browser made a total of 110 requests to load all elements on the main page. We found that 76% of them (84 requests) were addressed to the original Vivifi.me, 4% (4 requests) were made to Googletagmanager.com and 4% (4 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (3 sec) belongs to the original domain Vivifi.me.
Page size can be reduced by 5.1 MB (24%)
21.2 MB
16.1 MB
In fact, the total size of Vivifi.me main page is 21.2 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. 80% 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. Images take 20.1 MB which makes up the majority of the site volume.
Potential reduce by 482.8 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 482.8 kB or 92% of the original size.
Potential reduce by 4.6 MB
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, VIVIFI needs image optimization as it can save up to 4.6 MB or 23% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 5.0 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 5.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. Vivifi.me has all CSS files already compressed.
Number of requests can be reduced by 57 (58%)
99
42
The browser has sent 99 CSS, Javascripts, AJAX and image requests in order to completely render the main page of VIVIFI. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 31 to 1 for CSS and as a result speed up the page load time.
vivifi.me
509 ms
www.vivifi.me
1304 ms
gtm.js
96 ms
font-awesome.min.css
33 ms
dashicons.min.css
500 ms
extra.min.css
746 ms
style.min.css
995 ms
styles.css
747 ms
menu-image.css
751 ms
font-awesome.min.css
755 ms
swiper.min.css
752 ms
anicollection.css
999 ms
chosen.css
1002 ms
custom.css
1004 ms
responsive.css
1006 ms
js_composer.min.css
1016 ms
arprice_front.css
1246 ms
arptemplate_100.css
1243 ms
arptemplate_101.css
1244 ms
arptemplate_102.css
1254 ms
arptemplate_103.css
1255 ms
arptemplate_104.css
1268 ms
jquery.min.js
1741 ms
jquery-migrate.min.js
1497 ms
arprice_front.js
1494 ms
css2
42 ms
js
61 ms
analytics.js
18 ms
destination
127 ms
collect
66 ms
collect
62 ms
collect
137 ms
collect
152 ms
js
61 ms
arptemplate_100.css
1237 ms
css
53 ms
css
103 ms
css
102 ms
arptemplate_101.css
1236 ms
arptemplate_102.css
1252 ms
arptemplate_103.css
1686 ms
arptemplate_104.css
1687 ms
tabby.css
1703 ms
arprice_effects.css
1704 ms
wp-polyfill-inert.min.js
1705 ms
regenerator-runtime.min.js
1750 ms
wp-polyfill.min.js
1970 ms
index.js
1751 ms
jquery-3.3.1.min.js
1985 ms
anijs-min.js
1751 ms
anijs-helper-scrollreveal-min.js
1760 ms
api.js
118 ms
snippet.js
120 ms
getTrackingCode
39 ms
swiper.min.js
1991 ms
ga-audiences
15 ms
ga-audiences
13 ms
custom.js
1777 ms
chosen.jquery.js
1561 ms
index.js
1562 ms
js_composer_front.min.js
1799 ms
tabby.js
1801 ms
core.min.js
1801 ms
loader.gif
1594 ms
logo.png
707 ms
50_SharefRoamingPack_1920_740.png
1892 ms
50_SharefRoamingPack_800_800.png
2082 ms
50_offRoamingPack_1920_740.png
1848 ms
50_offRoamingPack_800_800.png
1841 ms
01-eSIM-Web-Desktop-1920x740x.png
2124 ms
01-eSIM-Web-Mobile-800x800x.png
1844 ms
Share-Summer-1-eSIM-Share-300GB-Web-1920-740-1.png
2591 ms
Ads-Mar24-Share-Summer-2-eSIM-Share-300GB-Web-800-800.png
2340 ms
02-Web-Plus-5G-1920-740x.png
2347 ms
02-Web-Plus5G-800-800x.png
2148 ms
03-Web-Plus-4G-1920-740x.png
2576 ms
03-Web-Plus4G-800-800x.png
2377 ms
05-Web-Binge-4G-1920-740x.png
2651 ms
04-Web-Binge-5G-800-800x.png
2592 ms
04-Web-Binge-5G-1920-740x.png
2601 ms
05-Web-Binge-4G-800-800x.png
2577 ms
6a-CIS180GB-5G-Web-1920-740x.png
2757 ms
6a-CIS180GB-5G-Web-800-800x.png
2768 ms
7-CIS170GB-Web-1920-740x.png
2770 ms
7-CIS170GB-Web-800-800x.png
2779 ms
fbevents.js
57 ms
pixie.js
106 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
105 ms
OpenSans-Regular.woff
2806 ms
rP2bp3im_k8G_wTVdvvMdHqmXTR3lEaLyKs.ttf
194 ms
fontawesome-webfont.woff
45 ms
OpenSans-SemiBold.woff
2784 ms
OpenSans-Bold.woff
2959 ms
OpenSans-ExtraBold.woff
2995 ms
fontawesome-webfont.woff
2994 ms
8-CISshare-Web-1920-740x.png
2772 ms
8-CISshare-Web-800-800x.png
2802 ms
9-OxSee-Watch-1920x740x.png
2803 ms
9-OxSee-Watch-800x800x.png
2938 ms
recaptcha__en.js
145 ms
right.png
2945 ms
left.png
2946 ms
Main_Banner_1920-300.png
2712 ms
lp.js
1005 ms
Main_Banner_800-300.png
2689 ms
vivifi.me-2.gif
2968 ms
Copy-of-vivifi.me_.gif
2711 ms
WhatsApp-Image-2020-03-17-at-3.57.19-PM.jpeg
2005 ms
scroll.png
1756 ms
tabby-print.css
253 ms
vivifi.me 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.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
vivifi.me 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
Page has valid source maps
vivifi.me SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Vivifi.me 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 Vivifi.me 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.
vivifi.me
Open Graph data is detected on the main page of VIVIFI. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: