Tools & Wizards About Us
pomelo.la screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

pomelo.la

Pomelo | Tecnología para tu negocio de tarjetas

Page Load Speed

1.6 sec in total

First Response

44 ms

Resources Loaded

1.1 sec

Page Rendered

512 ms

pomelo.la screenshot

About Website

Click here to check amazing Pomelo content for Argentina. Otherwise, check out these important facts you probably never knew about pomelo.la

Tecnología para emisión, procesamiento y gestión de tarjetas de crédito, débito y prepago en América Latina.

Visit pomelo.la

Key Findings

We analyzed Pomelo.la page load time and found that the first response time was 44 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

pomelo.la performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

20/100

10%

LCP (Largest Contentful Paint)

Value15.7 s

0/100

25%

SI (Speed Index)

Value8.6 s

17/100

10%

TBT (Total Blocking Time)

Value4,040 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value20.4 s

2/100

10%

Network Requests Diagram

pomelo.la

44 ms

pomelo.la

55 ms

194 ms

gtm.js

151 ms

newrelic.production.js

85 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 43% of them (18 requests) were addressed to the original Pomelo.la, 45% (19 requests) were made to Static.pomelo.la and 5% (2 requests) were made to Bam.nr-data.net. The less responsive or slowest element that took the longest time to load (532 ms) relates to the external source Static.pomelo.la.

Page Optimization Overview & Recommendations

Page size can be reduced by 263.1 kB (27%)

Content Size

971.8 kB

After Optimization

708.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pomelo.la main page is 971.8 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. HTML takes 479.3 kB which makes up the majority of the site volume.

HTML Optimization

-44%

Potential reduce by 209.6 kB

  • Original 479.3 kB
  • After minification 479.3 kB
  • After compression 269.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 209.6 kB or 44% of the original size.

Image Optimization

-11%

Potential reduce by 53.5 kB

  • Original 473.9 kB
  • After minification 420.4 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.

JavaScript Optimization

-0%

Potential reduce by 19 B

  • Original 18.3 kB
  • After minification 18.3 kB
  • After compression 18.3 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.

CSS Optimization

-4%

Potential reduce by 12 B

  • Original 282 B
  • After minification 282 B
  • After compression 270 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.

Requests Breakdown

Number of requests can be reduced by 14 (67%)

Requests Now

21

After Optimization

7

  • Images
  • JavaScript
  • CSS

The browser has sent 21 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 15 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

pomelo.la

pomelo.la

44 ms

pomelo.la

pomelo.la

55 ms

194 ms

gtm.js

gtm.js

151 ms

newrelic.production.js

newrelic.production.js

85 ms

18794d37168ff340.css

18794d37168ff340.css

47 ms

4df78f2cd73d6b26.css

4df78f2cd73d6b26.css

43 ms

polyfills-c67a75d1b6f99dc8.js

polyfills-c67a75d1b6f99dc8.js

41 ms

webpack-f2083eac8676b7d8.js

webpack-f2083eac8676b7d8.js

55 ms

framework-0ba0ddd33199226d.js

framework-0ba0ddd33199226d.js

82 ms

main-96569ce382ff3529.js

main-96569ce382ff3529.js

82 ms

_app-3922b8a1b56d8da0.js

_app-3922b8a1b56d8da0.js

154 ms

452-0c029c22d897a499.js

452-0c029c22d897a499.js

109 ms

365-7b31e64b1229e021.js

365-7b31e64b1229e021.js

254 ms

%5B%5B...pathParam%5D%5D-e6f46228e3757ed9.js

%5B%5B...pathParam%5D%5D-e6f46228e3757ed9.js

153 ms

_buildManifest.js

_buildManifest.js

152 ms

_ssgManifest.js

_ssgManifest.js

153 ms

hero.png

hero.png

247 ms

CardRappiLogo.png

CardRappiLogo.png

240 ms

TT-Norms-Pro.css

TT-Norms-Pro.css

253 ms

vcd15cbe7772f49c399c6a5babf22c1241717689176015

vcd15cbe7772f49c399c6a5babf22c1241717689176015

135 ms

nr-spa-1216.min.js

nr-spa-1216.min.js

85 ms

TT-Norms-Pro-Medium.woff

TT-Norms-Pro-Medium.woff

117 ms

TT-Norms-Pro-ExtraBlack.woff

TT-Norms-Pro-ExtraBlack.woff

239 ms

TT-Norms-Pro-ExtraLight.woff

TT-Norms-Pro-ExtraLight.woff

182 ms

TT-Norms-Pro-Thin.woff

TT-Norms-Pro-Thin.woff

201 ms

TT-Norms-Pro-Regular.woff

TT-Norms-Pro-Regular.woff

128 ms

TT-Norms-Pro-Light.woff

TT-Norms-Pro-Light.woff

199 ms

TT-Norms-Pro-Bold.woff

TT-Norms-Pro-Bold.woff

201 ms

TT-Norms-Pro-ExtraBold.woff

TT-Norms-Pro-ExtraBold.woff

295 ms

TT-Norms-Pro-Black.woff

TT-Norms-Pro-Black.woff

322 ms

TT-Norms-Pro-ExtraBlack-Italic.woff

TT-Norms-Pro-ExtraBlack-Italic.woff

370 ms

TT-Norms-Pro-ExtraLight-Italic.woff

TT-Norms-Pro-ExtraLight-Italic.woff

347 ms

TT-Norms-Pro-Thin-Italic.woff

TT-Norms-Pro-Thin-Italic.woff

354 ms

TT-Norms-Pro-Italic.woff

TT-Norms-Pro-Italic.woff

369 ms

TT-Norms-Pro-Medium-Italic.woff

TT-Norms-Pro-Medium-Italic.woff

377 ms

TT-Norms-Pro-Light-Italic.woff

TT-Norms-Pro-Light-Italic.woff

468 ms

TT-Norms-Pro-Bold-Italic.woff

TT-Norms-Pro-Bold-Italic.woff

458 ms

TT-Norms-Pro-ExtraBold-Italic.woff

TT-Norms-Pro-ExtraBold-Italic.woff

507 ms

TT-Norms-Pro-Black-Italic.woff

TT-Norms-Pro-Black-Italic.woff

532 ms

NRJS-510c438ea4a894d574f

NRJS-510c438ea4a894d574f

167 ms

NRJS-510c438ea4a894d574f

NRJS-510c438ea4a894d574f

81 ms

Accessibility Review

pomelo.la accessibility score

84

Accessibility Issues

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

High

Buttons do not have an accessible name

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

pomelo.la best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

pomelo.la SEO score

100

Search Engine Optimization Advices

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    ES

  • Encoding

    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.

Social Sharing Optimization

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: