7.7 sec in total
1.8 sec
5.4 sec
508 ms
Welcome to forevercash.com homepage info - get ready to check Forever Cash best content for United States right away, or after learning these important things about forevercash.com
Jack Bosch, author of Forever Cash, offers you sound financial advice to break the earn-spend cycle, take charge of your life, and build everlasting wealth.
Visit forevercash.comWe analyzed Forevercash.com page load time and found that the first response time was 1.8 sec and then it took 5.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
forevercash.com performance score
name
value
score
weighting
Value9.1 s
0/100
10%
Value13.4 s
0/100
25%
Value11.3 s
5/100
10%
Value770 ms
38/100
30%
Value0.275
44/100
15%
Value12.6 s
14/100
10%
1824 ms
7 ms
110 ms
88 ms
107 ms
Our browser made a total of 84 requests to load all elements on the main page. We found that 69% of them (58 requests) were addressed to the original Forevercash.com, 5% (4 requests) were made to Fonts.gstatic.com and 4% (3 requests) were made to D2ieqaiwehnqqp.cloudfront.net. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Forevercash.com.
Page size can be reduced by 949.5 kB (37%)
2.5 MB
1.6 MB
In fact, the total size of Forevercash.com 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. 65% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.
Potential reduce by 45.1 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. This page needs HTML code to be minified as it can gain 6.6 kB, which is 12% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 45.1 kB or 79% of the original size.
Potential reduce by 198.7 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, Forever Cash needs image optimization as it can save up to 198.7 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 245.8 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 245.8 kB or 66% of the original size.
Potential reduce by 459.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. Forevercash.com needs all CSS files to be minified and compressed as it can save up to 459.9 kB or 88% of the original size.
Number of requests can be reduced by 37 (49%)
76
39
The browser has sent 76 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Forever Cash. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
www.forevercash.com
1824 ms
jquery.min.js
7 ms
layerslider.css
110 ms
advanced-responsive-video-embedder-public.css
88 ms
bbpress.css
107 ms
styles.css
92 ms
plugin-styles.css
88 ms
wp-emoji-release.min.js
163 ms
video-js.css
37 ms
style.css
87 ms
core.css
105 ms
bootstrap.css
226 ms
bootstrap-responsive.css
136 ms
theme.css
366 ms
core.php
1461 ms
css
50 ms
jquery-2.2.0.min.js
144 ms
layerslider.kreaturamedia.jquery.js
147 ms
jquery-easing-1.3.js
149 ms
jquerytransit.js
152 ms
layerslider.transitions.js
153 ms
t0fd8b8de2717449cb23256e4a1cd30f5.js
60 ms
jquery-migrate-1.3.0.min.js
155 ms
run.js
156 ms
external-tracking.min.js
160 ms
widgets.js
58 ms
all.js
81 ms
plusone.js
90 ms
in.js
203 ms
editor.js
4 ms
core.min.js
5 ms
theme.js
9 ms
core.php
1219 ms
wp-embed.min.js
6 ms
jquery.tweet.js
7 ms
itrack360.appspot.com
110 ms
cb=gapi.loaded_0
45 ms
secureAnonymousFramework
105 ms
ga.js
41 ms
badge1.png
150 ms
bg_head_shadow.png
147 ms
bg_pattern1.png
148 ms
Forever-Cash-LOGO.png
35 ms
Forever-Cash-Logo-60.png
34 ms
free-kit-bg.jpg
147 ms
free-kit.png
316 ms
FC-book-3d-198x300.png
316 ms
bg_title_line.png
145 ms
FEC-047870x465.jpg
382 ms
bg_pattern2.png
168 ms
blogpost_text.png
171 ms
blog_author.png
171 ms
blog_date.png
316 ms
blog_categ.png
316 ms
blog_comments.png
317 ms
FEC-046870x465.jpg
335 ms
FEC-045870x465.jpg
491 ms
92 ms
bg_tweet_shadow.png
289 ms
bg_tweet_arrow.png
290 ms
xd_arbiter.php
70 ms
xd_arbiter.php
114 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
70 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
108 ms
EInbV5DfGHOiMmvb1Xr-honF5uFdDttMLvmWuJdhhgs.ttf
109 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
107 ms
__utm.gif
81 ms
bg_title_line2.png
227 ms
arrow.png
228 ms
ico_social-facebook.png
228 ms
ico_social-vimeo.png
228 ms
ico_social-twitter.png
229 ms
ico_social-pinterest.png
230 ms
ico_social-linked.png
230 ms
ico_social-youtube.png
235 ms
ico_social-google.png
236 ms
ico_social-instagram.png
236 ms
btn2top.png
274 ms
badge1.png
168 ms
user_timeline.json
39 ms
badge1.png
14 ms
sidebar-cta-button2.jpg
129 ms
g.js
6 ms
jquery.available.js
11 ms
forevercash.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
forevercash.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
forevercash.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Forevercash.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 Forevercash.com 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.
forevercash.com
Open Graph data is detected on the main page of Forever Cash. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: