Report Summary

  • 80

    Performance

    Renders faster than
    86% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

retirementphase.com

Crash Proof Retirement® Investments by Phil Cannella | Reviews & Testimonials | Crash Proof Retirement®

Page Load Speed

2.6 sec in total

First Response

298 ms

Resources Loaded

2 sec

Page Rendered

333 ms

retirementphase.com screenshot

About Website

Visit retirementphase.com now to see the best up-to-date Retirement Phase content and also check out these interesting facts you probably never knew about retirementphase.com

Crash Proof Retirement® Investments & Phil Cannella has been helping many people protect their investments & money for years. Visit our website to check out reviews on Crash Proof Retirement® by Phil ...

Visit retirementphase.com

Key Findings

We analyzed Retirementphase.com page load time and found that the first response time was 298 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

retirementphase.com performance score

80

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

70/100

10%

LCP (Largest Contentful Paint)

Value3.6 s

60/100

25%

SI (Speed Index)

Value2.4 s

98/100

10%

TBT (Total Blocking Time)

Value290 ms

80/100

30%

CLS (Cumulative Layout Shift)

Value0.01

100/100

15%

TTI (Time to Interactive)

Value3.2 s

94/100

10%

Network Requests Diagram

forum.php

298 ms

yuiloader-dom-event.js

283 ms

connection-min.js

152 ms

vbulletin-core.js

277 ms

jquery-1.6.1.min.js

318 ms

Our browser made a total of 75 requests to load all elements on the main page. We found that 89% of them (67 requests) were addressed to the original Retirementphase.com, 4% (3 requests) were made to Staticxx.facebook.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (603 ms) belongs to the original domain Retirementphase.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 340.7 kB (64%)

Content Size

531.9 kB

After Optimization

191.1 kB

In fact, the total size of Retirementphase.com main page is 531.9 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. 30% of websites need less resources to load. Javascripts take 287.7 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 50.7 kB

  • Original 63.3 kB
  • After minification 58.7 kB
  • After compression 12.6 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 50.7 kB or 80% of the original size.

Image Optimization

-2%

Potential reduce by 717 B

  • Original 29.7 kB
  • After minification 29.0 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. Retirement Phase images are well optimized though.

JavaScript Optimization

-56%

Potential reduce by 160.8 kB

  • Original 287.7 kB
  • After minification 283.9 kB
  • After compression 126.9 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 160.8 kB or 56% of the original size.

CSS Optimization

-85%

Potential reduce by 128.5 kB

  • Original 151.1 kB
  • After minification 116.8 kB
  • After compression 22.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. Retirementphase.com needs all CSS files to be minified and compressed as it can save up to 128.5 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 57 (77%)

Requests Now

74

After Optimization

17

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

Accessibility Review

retirementphase.com accessibility score

74

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.

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

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

retirementphase.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

retirementphase.com SEO score

85

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Retirementphase.com 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 Retirementphase.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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