Access pungle.ca. The Balance Blog | Branded Money & Finance Insights

Report Summary

About Website

Visit pungle.ca now to see the best up-to-date Pungle content and also check out these interesting facts you probably never knew about pungle.ca

Get the latest industry news on branded prepaid cards, custom payment platforms and loyalty programs and incentives from Berkeley Payments on our blog.

Visit pungle.ca

name

value

score

weighting

FCP (First Contentful Paint)

Value8.7 s

0/100

10%

LCP (Largest Contentful Paint)

Value16.8 s

0/100

25%

SI (Speed Index)

Value28.5 s

0/100

10%

TBT (Total Blocking Time)

Value43,290 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.038

100/100

15%

TTI (Time to Interactive)

Value59.7 s

0/100

10%

pungle.ca

110 ms

blog.berkeleypayment.com

231 ms

js

101 ms

wp-emoji-release.min.js

51 ms

vc-plugin.min.css

94 ms

Our browser made a total of 104 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Pungle.ca, 73% (76 requests) were made to Blog.berkeleypayment.com and 6% (6 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Blog.berkeleypayment.com.

Content Size

3.4 MB

After Optimization

2.5 MB

In fact, the total size of Pungle.ca main page is 3.4 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 2.3 MB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 316.1 kB

Original 354.5 kB
After minification 350.3 kB
After compression 38.5 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 316.1 kB or 89% of the original size.

Image Optimization

-8%

Potential reduce by 176.1 kB

Original 2.3 MB
After minification 2.2 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. Pungle images are well optimized though.

JavaScript Optimization

-18%

Potential reduce by 36.5 kB

Original 200.5 kB
After minification 200.5 kB
After compression 164.1 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 36.5 kB or 18% of the original size.

CSS Optimization

-67%

Potential reduce by 316.2 kB

Original 475.2 kB
After minification 475.0 kB
After compression 158.9 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. Pungle.ca needs all CSS files to be minified and compressed as it can save up to 316.2 kB or 67% of the original size.

Requests Now

100

After Optimization

The browser has sent 100 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pungle. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 36 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.

Accessibility Issues

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

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.

High

Form elements do not have associated labels

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

Search Engine Optimization Advices

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

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/).

High

Document uses legible font sizes

Language and Encoding

Language Detected

EN
Language Claimed

EN
Encoding

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pungle.ca 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 Pungle.ca 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

pungle.ca

Open Graph data is detected on the main page of Pungle. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook:

Report Summary

Performance

Accessibility

Best Practices

SEO

The Balance Blog | Branded Money & Finance Insights

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)