1.1 sec in total
115 ms
831 ms
153 ms
Welcome to tomato.ph homepage info - get ready to check Tomato best content for Philippines right away, or after learning these important things about tomato.ph
Visit tomato.phWe analyzed Tomato.ph page load time and found that the first response time was 115 ms and then it took 984 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.
tomato.ph performance score
115 ms
7 ms
11 ms
17 ms
16 ms
Our browser made a total of 49 requests to load all elements on the main page. We found that 80% of them (39 requests) were addressed to the original Tomato.ph, 10% (5 requests) were made to Google-analytics.com and 4% (2 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (307 ms) relates to the external source Static.xx.fbcdn.net.
Page size can be reduced by 500.8 kB (43%)
1.2 MB
654.0 kB
In fact, the total size of Tomato.ph main page is 1.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. 55% of websites need less resources to load. Images take 540.9 kB which makes up the majority of the site volume.
Potential reduce by 45.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. This page needs HTML code to be minified as it can gain 9.7 kB, which is 17% 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 45.2 kB or 78% of the original size.
Potential reduce by 85.1 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. Obviously, Tomato needs image optimization as it can save up to 85.1 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 310.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 310.4 kB or 64% of the original size.
Potential reduce by 60.0 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. Tomato.ph needs all CSS files to be minified and compressed as it can save up to 60.0 kB or 84% of the original size.
Number of requests can be reduced by 25 (53%)
47
22
The browser has sent 47 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tomato. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
www.tomato.ph
115 ms
ModuleStyleSheets.css
7 ms
tomato-global.css
11 ms
jquery-1.7.1.min.js
17 ms
jquery.cycle.all.js
16 ms
cufon-yui.js
13 ms
HelveticaNeueThinExt_100.font.js
15 ms
jquery.jcarousel.min.js
15 ms
script-homepagetemplate.js
16 ms
newdesigncss.css
39 ms
jquery.countdown.js
41 ms
jquery-1.4.2.min.js
45 ms
skin.css
43 ms
jquery.countdown.css
43 ms
Box.css
44 ms
Java_OnlineShopping.js
56 ms
Java_Cookies.js
55 ms
Java_Box.js
55 ms
prototype-core.ashx
60 ms
CMS.CatalogueRetrieve,Catalyst.Web.CMS.ashx
62 ms
conversion.js
68 ms
Java_DynMenusSelectedCSS.js
58 ms
ValidationFunctions.js
82 ms
htmlbg.jpg
94 ms
Java_OnlineShopping.aspx
76 ms
BTSrepeating.jpg
67 ms
2016_generic_banner.jpg
72 ms
ArrowMenuRight.gif
68 ms
homepage-renovation.jpg
71 ms
Payment%20Footer%20new.png
68 ms
facebook.png
67 ms
twitter.png
68 ms
pinterest.png
70 ms
youtube.png
68 ms
Instagram.png
69 ms
ga.js
70 ms
gtm.js
68 ms
analytics.js
65 ms
banner_arrow_left.jpg
57 ms
banner_arrow_right.jpg
57 ms
ValidationFunctions.aspx
56 ms
shoppingcart.png
36 ms
globalsign.jpg
36 ms
__utm.gif
13 ms
collect
10 ms
like.php
139 ms
vpc6VNjRPXV.js
271 ms
LVx-xkvaJ0b.png
307 ms
collect
11 ms
tomato.ph SEO score
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tomato.ph can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Tomato.ph 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.
tomato.ph
Open Graph description is not detected on the main page of Tomato. 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: