Tools & Wizards About Us
johnjamesforsenate.com screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 62% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

johnjamesforsenate.com

Home - John James for Congress

Page Load Speed

8.4 sec in total

First Response

336 ms

Resources Loaded

5.2 sec

Page Rendered

2.9 sec

johnjamesforsenate.com screenshot

About Website

Click here to check amazing John James Forsenate content for United States. Otherwise, check out these important facts you probably never knew about johnjamesforsenate.com

Fighting for the American Dream.

Visit johnjamesforsenate.com

Key Findings

We analyzed Johnjamesforsenate.com page load time and found that the first response time was 336 ms and then it took 8.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

johnjamesforsenate.com performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

37/100

10%

LCP (Largest Contentful Paint)

Value16.7 s

0/100

25%

SI (Speed Index)

Value9.8 s

10/100

10%

TBT (Total Blocking Time)

Value5,260 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value22.2 s

1/100

10%

Network Requests Diagram

johnjamesforsenate.com

336 ms

johnjamesforsenate.com

588 ms

wp-emoji-release.min.js

43 ms

style.min.css

48 ms

styles.css

92 ms

Our browser made a total of 138 requests to load all elements on the main page. We found that 51% of them (71 requests) were addressed to the original Johnjamesforsenate.com, 25% (35 requests) were made to Youtube.com and 2% (3 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (2.2 sec) relates to the external source Google.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (58%)

Content Size

2.0 MB

After Optimization

840.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Johnjamesforsenate.com main page is 2.0 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. 85% 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. CSS take 906.0 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 55.8 kB

  • Original 70.8 kB
  • After minification 70.7 kB
  • After compression 15.0 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 55.8 kB or 79% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 449.1 kB
  • After minification 449.1 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. John James Forsenate images are well optimized though.

JavaScript Optimization

-61%

Potential reduce by 363.4 kB

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

CSS Optimization

-84%

Potential reduce by 763.5 kB

  • Original 906.0 kB
  • After minification 905.2 kB
  • After compression 142.5 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. Johnjamesforsenate.com needs all CSS files to be minified and compressed as it can save up to 763.5 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 75 (70%)

Requests Now

107

After Optimization

32

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

johnjamesforsenate.com

johnjamesforsenate.com

336 ms

johnjamesforsenate.com

johnjamesforsenate.com

588 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

43 ms

style.min.css

style.min.css

48 ms

styles.css

styles.css

92 ms

bootstrap.min.css

bootstrap.min.css

70 ms

magnific.css

magnific.css

66 ms

style.css

style.css

79 ms

formreset.min.css

formreset.min.css

108 ms

formsmain.min.css

formsmain.min.css

98 ms

readyclass.min.css

readyclass.min.css

110 ms

browsers.min.css

browsers.min.css

136 ms

font-awesome.min.css

font-awesome.min.css

122 ms

ec.css

ec.css

118 ms

vss.css

vss.css

138 ms

css

css

108 ms

slick.css

slick.css

119 ms

slick-theme.css

slick-theme.css

133 ms

jquery.js

jquery.js

137 ms

jquery-migrate.min.js

jquery-migrate.min.js

130 ms

powered-by.js

powered-by.js

133 ms

fts-global.js

fts-global.js

136 ms

gtm4wp-form-move-tracker.js

gtm4wp-form-move-tracker.js

135 ms

responsive-modernizr.js

responsive-modernizr.js

137 ms

magnific.min.js

magnific.min.js

138 ms

bootstrap.js

bootstrap.js

143 ms

strap-extras.js

strap-extras.js

146 ms

jquery.json.min.js

jquery.json.min.js

142 ms

gravityforms.min.js

gravityforms.min.js

146 ms

jquery.maskedinput.min.js

jquery.maskedinput.min.js

155 ms

placeholders.jquery.min.js

placeholders.jquery.min.js

154 ms

gf.placeholders.js

gf.placeholders.js

154 ms

email-decode.min.js

email-decode.min.js

144 ms

fitToWidth.js

fitToWidth.js

163 ms

css

css

108 ms

ec.js

ec.js

161 ms

slick.min.js

slick.min.js

153 ms

vss.js

vss.js

167 ms

jquery.waypoints.js

jquery.waypoints.js

120 ms

custom.js

custom.js

165 ms

responsive-scripts.js

responsive-scripts.js

181 ms

responsive-plugins.js

responsive-plugins.js

158 ms

comment-reply.min.js

comment-reply.min.js

139 ms

bootstrap-hover-dropdown.js

bootstrap-hover-dropdown.js

114 ms

style.css

style.css

113 ms

imgeDefaultStyles.css

imgeDefaultStyles.css

103 ms

jquery.ellipsis.js

jquery.ellipsis.js

90 ms

parallax.js

parallax.js

339 ms

ie_prototype_fixes.js

ie_prototype_fixes.js

325 ms

mga_scripts.js

mga_scripts.js

331 ms

detectmobilebrowser.min.js

detectmobilebrowser.min.js

315 ms

wp-embed.min.js

wp-embed.min.js

324 ms

gtm.js

gtm.js

180 ms

john_james_logo.png

john_james_logo.png

140 ms

action-center-bg.png

action-center-bg.png

1175 ms

play-btn.png

play-btn.png

136 ms

john_flag.png

john_flag.png

167 ms

JJ_Web_FullSite_CopterAnimation_Transparent.gif

JJ_Web_FullSite_CopterAnimation_Transparent.gif

380 ms

JJ_Web_FullSite_ProgressBar_3-4.gif

JJ_Web_FullSite_ProgressBar_3-4.gif

164 ms

store_item_profile_sign.png

store_item_profile_sign.png

164 ms

store_item_shirts-1.png

store_item_shirts-1.png

209 ms

store_item_sign.png

store_item_sign.png

206 ms

store_item_hat.png

store_item_hat.png

208 ms

Action-Center-2-1024x768.jpeg

Action-Center-2-1024x768.jpeg

205 ms

image003-1024x768.jpg

image003-1024x768.jpg

210 ms

image001-1024x918.jpg

image001-1024x918.jpg

210 ms

Novecentosanswide-Bold-webfont.woff

Novecentosanswide-Bold-webfont.woff

212 ms

Novecentosanswide-DemiBold-webfont.woff

Novecentosanswide-DemiBold-webfont.woff

211 ms

Novecentosanswide-Medium-webfont.woff

Novecentosanswide-Medium-webfont.woff

212 ms

Novecentosanswide-Normal-webfont.woff

Novecentosanswide-Normal-webfont.woff

212 ms

Novecentosanswide-Book-webfont.woff

Novecentosanswide-Book-webfont.woff

248 ms

Novecentosanswide-Light-webfont.woff

Novecentosanswide-Light-webfont.woff

248 ms

qkBWXvYC6trAT7zuC8m5xL4.ttf

qkBWXvYC6trAT7zuC8m5xL4.ttf

212 ms

qkBbXvYC6trAT7RVLtk.ttf

qkBbXvYC6trAT7RVLtk.ttf

246 ms

conversion_async.js

conversion_async.js

528 ms

analytics.js

analytics.js

268 ms

uwt.js

uwt.js

507 ms

ytc.js

ytc.js

506 ms

helmet.png

helmet.png

85 ms

TABrqMs12MA

TABrqMs12MA

299 ms

WxtPxbGXjs8

WxtPxbGXjs8

303 ms

dd8byG5wiTM

dd8byG5wiTM

307 ms

m77mSr517no

m77mSr517no

310 ms

TAi-7cuxSwg

TAi-7cuxSwg

312 ms

7OX6OmVEMM0

7OX6OmVEMM0

333 ms

rPlOWgS9WAI

rPlOWgS9WAI

335 ms

64EPWuKGVGA

64EPWuKGVGA

338 ms

kLOXBqj7nFI

kLOXBqj7nFI

340 ms

WxtPxbGXjs8

WxtPxbGXjs8

840 ms

dd8byG5wiTM

dd8byG5wiTM

665 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

378 ms

iframe_api

iframe_api

636 ms

TABrqMs12MA

TABrqMs12MA

50 ms

WxtPxbGXjs8

WxtPxbGXjs8

46 ms

dd8byG5wiTM

dd8byG5wiTM

42 ms

m77mSr517no

m77mSr517no

38 ms

TAi-7cuxSwg

TAi-7cuxSwg

35 ms

7OX6OmVEMM0

7OX6OmVEMM0

13 ms

rPlOWgS9WAI

rPlOWgS9WAI

11 ms

64EPWuKGVGA

64EPWuKGVGA

7 ms

kLOXBqj7nFI

kLOXBqj7nFI

4 ms

js

js

225 ms

mem8YaGs126MiZpBA-UFVZ0e.ttf

mem8YaGs126MiZpBA-UFVZ0e.ttf

72 ms

fbevents.js

fbevents.js

373 ms

tc.min.js

tc.min.js

592 ms

TABrqMs12MA

TABrqMs12MA

447 ms

WxtPxbGXjs8

WxtPxbGXjs8

425 ms

dd8byG5wiTM

dd8byG5wiTM

446 ms

m77mSr517no

m77mSr517no

445 ms

TAi-7cuxSwg

TAi-7cuxSwg

449 ms

7OX6OmVEMM0

7OX6OmVEMM0

787 ms

rPlOWgS9WAI

rPlOWgS9WAI

787 ms

64EPWuKGVGA

64EPWuKGVGA

787 ms

kLOXBqj7nFI

kLOXBqj7nFI

786 ms

415 ms

10099221.json

10099221.json

160 ms

adsct

adsct

1723 ms

collect

collect

130 ms

www-player.css

www-player.css

134 ms

www-embed-player.js

www-embed-player.js

261 ms

base.js

base.js

588 ms

fetch-polyfill.js

fetch-polyfill.js

494 ms

sp.pl

sp.pl

575 ms

www-widgetapi.js

www-widgetapi.js

489 ms

oct.js

oct.js

82 ms

2048050758748417

2048050758748417

66 ms

collect

collect

1633 ms

def_print_styles.css

def_print_styles.css

364 ms

adsct

adsct

1579 ms

pixel

pixel

370 ms

2009 ms

2156 ms

idr.js

idr.js

1914 ms

id

id

750 ms

ad_status.js

ad_status.js

944 ms

ga-audiences

ga-audiences

905 ms

embed.js

embed.js

437 ms

36t2pzUCsky2p8StOfRDuZ2SQrRQGkwFUvrIpVyovYo.js

36t2pzUCsky2p8StOfRDuZ2SQrRQGkwFUvrIpVyovYo.js

298 ms

Accessibility Review

johnjamesforsenate.com accessibility score

86

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

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

johnjamesforsenate.com 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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

johnjamesforsenate.com 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

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Johnjamesforsenate.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 Johnjamesforsenate.com main page’s claimed encoding is . 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

johnjamesforsenate.com

Open Graph data is detected on the main page of John James Forsenate. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: