Tools & Wizards About Us
petermacfarlane.info screenshot

Report Summary

  • 34

    Performance

    Renders faster than
    54% of other websites

  • 69

    Accessibility

    Visual factors better than
    that of 34% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

petermacfarlane.info

Global financial matters, personal privacy, and offshore wealth creation.

Page Load Speed

8 sec in total

First Response

1.1 sec

Resources Loaded

6.8 sec

Page Rendered

125 ms

petermacfarlane.info screenshot

About Website

Welcome to petermacfarlane.info homepage info - get ready to check Petermacfarlane best content right away, or after learning these important things about petermacfarlane.info

Compliant Asset Protection and Capital Preservation structures, Precious Metals transactions, Citizenship and residency planning, Offshore investment for tax-free growth and E-commerce and payment sys...

Visit petermacfarlane.info

Key Findings

We analyzed Petermacfarlane.info page load time and found that the first response time was 1.1 sec and then it took 6.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

petermacfarlane.info performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.6 s

0/100

10%

LCP (Largest Contentful Paint)

Value8.3 s

2/100

25%

SI (Speed Index)

Value18.4 s

0/100

10%

TBT (Total Blocking Time)

Value480 ms

59/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value17.9 s

4/100

10%

Network Requests Diagram

www.petermacfarlane.info

1142 ms

wp-emoji-release.min.js

265 ms

style.min.css

265 ms

styles.css

262 ms

rs6.css

270 ms

Our browser made a total of 64 requests to load all elements on the main page. We found that 73% of them (47 requests) were addressed to the original Petermacfarlane.info, 20% (13 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Petermacfarlane.info.

Page Optimization Overview & Recommendations

Page size can be reduced by 97.5 kB (4%)

Content Size

2.5 MB

After Optimization

2.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Petermacfarlane.info main page is 2.5 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. 50% of websites need less resources to load. Images take 1.9 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 75.6 kB

  • Original 94.8 kB
  • After minification 94.8 kB
  • After compression 19.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. 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 75.6 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 5.1 kB

  • Original 1.9 MB
  • After minification 1.9 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. Petermacfarlane images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 5.8 kB

  • Original 367.0 kB
  • After minification 367.0 kB
  • After compression 361.2 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

-11%

Potential reduce by 11.0 kB

  • Original 98.6 kB
  • After minification 98.5 kB
  • After compression 87.7 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. Petermacfarlane.info needs all CSS files to be minified and compressed as it can save up to 11.0 kB or 11% of the original size.

Requests Breakdown

Number of requests can be reduced by 38 (79%)

Requests Now

48

After Optimization

10

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.petermacfarlane.info

www.petermacfarlane.info

1142 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

265 ms

style.min.css

style.min.css

265 ms

styles.css

styles.css

262 ms

rs6.css

rs6.css

270 ms

style.css

style.css

290 ms

base.css

base.css

307 ms

layout.css

layout.css

635 ms

shortcodes.css

shortcodes.css

621 ms

animations.min.css

animations.min.css

509 ms

jquery.ui.all.css

jquery.ui.all.css

498 ms

jplayer.blue.monday.css

jplayer.blue.monday.css

529 ms

responsive.css

responsive.css

540 ms

css

css

41 ms

jquery.min.js

jquery.min.js

851 ms

jquery-migrate.min.js

jquery-migrate.min.js

740 ms

rbtools.min.js

rbtools.min.js

993 ms

rs6.min.js

rs6.min.js

1012 ms

css

css

14 ms

wp-polyfill.min.js

wp-polyfill.min.js

909 ms

index.js

index.js

812 ms

core.min.js

core.min.js

918 ms

mouse.min.js

mouse.min.js

1030 ms

sortable.min.js

sortable.min.js

1079 ms

tabs.min.js

tabs.min.js

1149 ms

accordion.min.js

accordion.min.js

1161 ms

plugins.js

plugins.js

1406 ms

menu.js

menu.js

1169 ms

animations.min.js

animations.min.js

1257 ms

jplayer.min.js

jplayer.min.js

1318 ms

translate3d.js

translate3d.js

1392 ms

scripts.js

scripts.js

1512 ms

wp-embed.min.js

wp-embed.min.js

1407 ms

home_it_subheader.jpg

home_it_subheader.jpg

855 ms

logo.png

logo.png

707 ms

InternetMarketers2.jpg

InternetMarketers2.jpg

1121 ms

Banking.jpg

Banking.jpg

1257 ms

passports.jpg

passports.jpg

692 ms

consulting.jpg

consulting.jpg

1246 ms

corporative-services2.jpg

corporative-services2.jpg

1829 ms

local-ga.js

local-ga.js

995 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

52 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

65 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

87 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

92 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

93 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCIPrQ.ttf

92 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrQ.ttf

92 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCIPrQ.ttf

93 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf

108 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrQ.ttf

111 ms

KFOkCnqEu92Fr1Mu51xIIzc.ttf

KFOkCnqEu92Fr1Mu51xIIzc.ttf

110 ms

KFOjCnqEu92Fr1Mu51TzBic6CsE.ttf

KFOjCnqEu92Fr1Mu51TzBic6CsE.ttf

110 ms

mfn-icons.woff

mfn-icons.woff

1246 ms

wp-polyfill-fetch.min.js

wp-polyfill-fetch.min.js

1189 ms

wp-polyfill-dom-rect.min.js

wp-polyfill-dom-rect.min.js

1265 ms

wp-polyfill-url.min.js

wp-polyfill-url.min.js

1377 ms

wp-polyfill-formdata.min.js

wp-polyfill-formdata.min.js

1390 ms

wp-polyfill-element-closest.min.js

wp-polyfill-element-closest.min.js

1425 ms

wp-polyfill-object-fit.min.js

wp-polyfill-object-fit.min.js

1434 ms

S6u9w4BMUTPHh50XSwiPHA.ttf

S6u9w4BMUTPHh50XSwiPHA.ttf

63 ms

collect

collect

28 ms

js

js

66 ms

box_shadow.png

box_shadow.png

239 ms

Accessibility Review

petermacfarlane.info accessibility score

69

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

petermacfarlane.info best practices score

67

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

petermacfarlane.info 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

    EN

  • Encoding

    UTF-8

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

petermacfarlane.info

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