Access jimrogers1.blogspot.ca. JIM ROGERS BLOG

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

44/100

10%

LCP (Largest Contentful Paint)

Value3.3 s

68/100

25%

SI (Speed Index)

Value5.5 s

55/100

10%

TBT (Total Blocking Time)

Value3,820 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.07

96/100

15%

TTI (Time to Interactive)

Value11.8 s

17/100

10%

jimrogers1.blogspot.ca

106 ms

webfont.js

13 ms

3375562265-css_bundle_v2.css

60 ms

authorization.css

130 ms

plusone.js

68 ms

Our browser made a total of 131 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Jimrogers1.blogspot.ca, 10% (13 requests) were made to Apis.google.com and 6% (8 requests) were made to Cm.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Connect.facebook.net.

Content Size

1.8 MB

After Optimization

706.8 kB

In fact, the total size of Jimrogers1.blogspot.ca main page is 1.8 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. Javascripts take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 118.9 kB

Original 158.6 kB
After minification 157.8 kB
After compression 39.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 118.9 kB or 75% of the original size.

Image Optimization

-2%

Potential reduce by 3.9 kB

Original 195.6 kB
After minification 191.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. JIM ROGERS 1 BLOG Spot images are well optimized though.

JavaScript Optimization

-63%

Potential reduce by 725.5 kB

Original 1.2 MB
After minification 1.1 MB
After compression 425.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 725.5 kB or 63% of the original size.

CSS Optimization

-80%

Potential reduce by 202.6 kB

Original 252.2 kB
After minification 252.1 kB
After compression 49.6 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. Jimrogers1.blogspot.ca needs all CSS files to be minified and compressed as it can save up to 202.6 kB or 80% of the original size.

Requests Now

117

After Optimization

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

Accessibility Issues

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

High

[aria-*] attributes do not match their roles

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

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

High

Image elements do not have [alt] attributes

These items highlight common accessibility best practices.

High

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

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

High

Serves images with low resolution

High

Browser errors were logged to the console

High

Page has valid source maps

Search Engine Optimization Advices

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

High

Image elements do not have [alt] attributes

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

High

Tap targets are not sized appropriately

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 Jimrogers1.blogspot.ca 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 Jimrogers1.blogspot.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

jimrogers1.blogspot.ca

Open Graph description is not detected on the main page of JIM ROGERS 1 BLOG Spot. 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:

Report Summary

Performance

Accessibility

Best Practices

SEO

JIM ROGERS BLOG

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)

Network Requests Diagram

jimrogers1.blogspot.ca

webfont.js

3375562265-css_bundle_v2.css

authorization.css

plusone.js

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

jimrogers1.blogspot.ca

webfont.js

3375562265-css_bundle_v2.css

authorization.css

plusone.js

show_ads.js

addthis_widget.js

widget.js

3226477086-widgets.js

css

cb=gapi.loaded_0

cb=gapi.loaded_1

google_top_exp.js

cooltext161166594221344.png

Jim-Rogers.jpeg

icon18_wrench_allbkg.png

ca-pub-7311859719012289.js

zrt_lookup.html

show_ads_impl.js

player

icon18_edit_allbkg.gif

hqdefault.jpg

MZ5rAof-p_E

get_custom_js

pixel.png

feed-icon16x16.png

default.jpg

index.jpeg

images.jpg

default.jpg

default.jpg

cb=gapi.loaded_2

fastbutton

stats

300lo.json

all.js&version=v2.0

widgets.js

pinit00.png

counter.5524cceca805eb4b9b2b.js

WJ6D195CfbTRlIs49IbkFw.woff

0Aa8aBJcGN1n1zDNhqNrnQ.woff

NbE6ykYuM2IyEwxQxOIi2Hl4twXkwp3_u9ZoePkT564.woff

sh.8e5f85691f9aaa082472a194.html