1.5 sec in total
75 ms
1.1 sec
323 ms
Click here to check amazing Pomelo content for Argentina. Otherwise, check out these important facts you probably never knew about pomelo.la
At Pomelo, we develop technological infrastructure to enable you to launch and enhance your fintech. Discover more!
Visit pomelo.laWe analyzed Pomelo.la page load time and found that the first response time was 75 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
pomelo.la performance score
name
value
score
weighting
Value2.3 s
76/100
10%
Value12.8 s
0/100
25%
Value7.7 s
24/100
10%
Value3,470 ms
2/100
30%
Value0.093
91/100
15%
Value14.7 s
8/100
10%
75 ms
89 ms
74 ms
66 ms
55 ms
Our browser made a total of 46 requests to load all elements on the main page. We found that 37% of them (17 requests) were addressed to the original Pomelo.la, 41% (19 requests) were made to Static.pomelo.la and 7% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (551 ms) relates to the external source Static.pomelo.la.
Page size can be reduced by 189.6 kB (28%)
684.3 kB
494.7 kB
In fact, the total size of Pomelo.la main page is 684.3 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. 70% of websites need less resources to load. Images take 473.9 kB which makes up the majority of the site volume.
Potential reduce by 136.0 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 136.0 kB or 71% of the original size.
Potential reduce by 53.5 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, Pomelo needs image optimization as it can save up to 53.5 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 73 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 23 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. Pomelo.la has all CSS files already compressed.
Number of requests can be reduced by 19 (73%)
26
7
The browser has sent 26 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pomelo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and as a result speed up the page load time.
pomelo.la
75 ms
89 ms
gtm.js
74 ms
newrelic.production.js
66 ms
e62c4be4f79dccc4.css
55 ms
4df78f2cd73d6b26.css
29 ms
polyfills-c67a75d1b6f99dc8.js
39 ms
webpack-ac2f55fe4efd6500.js
74 ms
framework-0ba0ddd33199226d.js
61 ms
main-96569ce382ff3529.js
61 ms
_app-c32459125558247f.js
165 ms
0-2d4008a4c4803bec.js
129 ms
879-552a932e4cab8f36.js
163 ms
%5B%5B...pathParam%5D%5D-6fb904ff673cdce5.js
128 ms
_buildManifest.js
129 ms
_ssgManifest.js
161 ms
hero.png
284 ms
CardRappiLogo.png
182 ms
v84a3a4012de94ce1a686ba8c167c359c1696973893317
131 ms
TT-Norms-Pro.css
134 ms
js
64 ms
insight.min.js
240 ms
destination
188 ms
hotjar-3823799.js
244 ms
TT-Norms-Pro-ExtraBlack.woff
217 ms
TT-Norms-Pro-ExtraLight.woff
160 ms
TT-Norms-Pro-Thin.woff
252 ms
TT-Norms-Pro-Regular.woff
83 ms
TT-Norms-Pro-Medium.woff
117 ms
TT-Norms-Pro-Light.woff
117 ms
TT-Norms-Pro-Bold.woff
118 ms
TT-Norms-Pro-ExtraBold.woff
314 ms
TT-Norms-Pro-Black.woff
198 ms
TT-Norms-Pro-ExtraBlack-Italic.woff
258 ms
TT-Norms-Pro-ExtraLight-Italic.woff
551 ms
TT-Norms-Pro-Thin-Italic.woff
382 ms
TT-Norms-Pro-Italic.woff
257 ms
TT-Norms-Pro-Medium-Italic.woff
420 ms
TT-Norms-Pro-Light-Italic.woff
402 ms
TT-Norms-Pro-Bold-Italic.woff
470 ms
TT-Norms-Pro-ExtraBold-Italic.woff
490 ms
TT-Norms-Pro-Black-Italic.woff
542 ms
76 ms
modules.a4fd7e5489291affcf56.js
24 ms
58 ms
nr-spa-1216.min.js
23 ms
pomelo.la accessibility score
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
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
pomelo.la 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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
pomelo.la SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
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
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pomelo.la can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Spanish language. Our system also found out that Pomelo.la 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.
pomelo.la
Open Graph data is detected on the main page of Pomelo. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: