Report Summary

  • 65

    Performance

    Renders faster than
    78% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

pocketsmith.ph

PocketSmith - Smart personal finance software. Remember bills, budget for the future, organize your money in a calendar.

Page Load Speed

519 ms in total

First Response

114 ms

Resources Loaded

308 ms

Page Rendered

97 ms

pocketsmith.ph screenshot

About Website

Welcome to pocketsmith.ph homepage info - get ready to check Pocket Smith best content right away, or after learning these important things about pocketsmith.ph

PocketSmith is a personal finance and budgeting application. Organize your money in a calendar, remember bills, budget for the future and reduce debt.

Visit pocketsmith.ph

Key Findings

We analyzed Pocketsmith.ph page load time and found that the first response time was 114 ms and then it took 405 ms to load all DOM resources and completely render a web page. This is an excellent result, as only 5% of websites can load faster.

Performance Metrics

pocketsmith.ph performance score

65

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

59/100

10%

LCP (Largest Contentful Paint)

Value6.3 s

11/100

25%

SI (Speed Index)

Value3.3 s

90/100

10%

TBT (Total Blocking Time)

Value240 ms

85/100

30%

CLS (Cumulative Layout Shift)

Value0.088

92/100

15%

TTI (Time to Interactive)

Value4.8 s

79/100

10%

Network Requests Diagram

pocketsmith.ph

114 ms

style.css

16 ms

enhance.js

6 ms

euz.net

33 ms

iq

151 ms

Our browser made a total of 7 requests to load all elements on the main page. We found that 43% of them (3 requests) were addressed to the original Pocketsmith.ph, 14% (1 request) were made to Parking.parklogic.com and 14% (1 request) were made to Euz.net. The less responsive or slowest element that took the longest time to load (151 ms) relates to the external source Q.dreniq.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 10.9 kB (39%)

Content Size

27.9 kB

After Optimization

17.0 kB

In fact, the total size of Pocketsmith.ph main page is 27.9 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only 5% of websites need less resources to load. Images take 15.1 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 8.2 kB

  • Original 9.9 kB
  • After minification 9.9 kB
  • After compression 1.7 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 8.2 kB or 83% of the original size.

Image Optimization

-6%

Potential reduce by 866 B

  • Original 15.1 kB
  • After minification 14.3 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. Pocket Smith images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 1.6 kB

  • Original 2.5 kB
  • After minification 2.2 kB
  • After compression 884 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 1.6 kB or 65% of the original size.

CSS Optimization

-59%

Potential reduce by 220 B

  • Original 372 B
  • After minification 276 B
  • After compression 152 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. Pocketsmith.ph needs all CSS files to be minified and compressed as it can save up to 220 B or 59% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

5

After Optimization

5

The browser has sent 5 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pocket Smith. According to our analytics all requests are already optimized.

Accessibility Review

pocketsmith.ph accessibility score

94

Accessibility Issues

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.

Best Practices

pocketsmith.ph best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

pocketsmith.ph SEO score

75

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pocketsmith.ph can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Pocketsmith.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.

Social Sharing Optimization

Open Graph description is not detected on the main page of Pocket Smith. 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: