Tools & Wizards About Us
standwithmike.org screenshot

Report Summary

  • 75

    Performance

    Renders faster than
    83% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 88

    SEO

    Google-friendlier than
    65% of websites

standwithmike.org

STAND WITH MIKE McCARRON - HOME

Page Load Speed

4.5 sec in total

First Response

1.8 sec

Resources Loaded

2.5 sec

Page Rendered

239 ms

standwithmike.org screenshot

About Website

Click here to check amazing STAND WITH MIKE content. Otherwise, check out these important facts you probably never knew about standwithmike.org

Site to support Mike McCarron of

Visit standwithmike.org

Key Findings

We analyzed Standwithmike.org page load time and found that the first response time was 1.8 sec and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

standwithmike.org performance score

75

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

40/100

10%

LCP (Largest Contentful Paint)

Value3.9 s

51/100

25%

SI (Speed Index)

Value4.7 s

70/100

10%

TBT (Total Blocking Time)

Value10 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.124

83/100

15%

TTI (Time to Interactive)

Value3.6 s

92/100

10%

Network Requests Diagram

standwithmike.org

1797 ms

sites.css

256 ms

fancybox.css

135 ms

main_style.css

77 ms

css

51 ms

Our browser made a total of 25 requests to load all elements on the main page. We found that 60% of them (15 requests) were addressed to the original Standwithmike.org, 20% (5 requests) were made to Www2.dragndropbuilder.com and 8% (2 requests) were made to Assets.www2.dragndropbuilder.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Standwithmike.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 202.3 kB (50%)

Content Size

401.8 kB

After Optimization

199.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Standwithmike.org main page is 401.8 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. 20% of websites need less resources to load. Images take 160.6 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 11.3 kB

  • Original 14.6 kB
  • After minification 14.3 kB
  • After compression 3.3 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 11.3 kB or 77% of the original size.

Image Optimization

-9%

Potential reduce by 15.1 kB

  • Original 160.6 kB
  • After minification 145.5 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. STAND WITH MIKE images are well optimized though.

JavaScript Optimization

-72%

Potential reduce by 80.4 kB

  • Original 111.2 kB
  • After minification 97.8 kB
  • After compression 30.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 80.4 kB or 72% of the original size.

CSS Optimization

-83%

Potential reduce by 95.5 kB

  • Original 115.4 kB
  • After minification 110.4 kB
  • After compression 19.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. Standwithmike.org needs all CSS files to be minified and compressed as it can save up to 95.5 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 9 (39%)

Requests Now

23

After Optimization

14

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

standwithmike.org

standwithmike.org

1797 ms

sites.css

sites.css

256 ms

fancybox.css

fancybox.css

135 ms

main_style.css

main_style.css

77 ms

css

css

51 ms

slideshow.css

slideshow.css

135 ms

jquery.min.js

jquery.min.js

86 ms

main.js

main.js

319 ms

slideshow-jq.js

slideshow-jq.js

276 ms

social-no-container-blue.png

social-no-container-blue.png

107 ms

no-header-wrap-in-blue.png

no-header-wrap-in-blue.png

133 ms

nav-blue.png

nav-blue.png

134 ms

nav-current-blue.png

nav-current-blue.png

146 ms

nav-sep.png

nav-sep.png

136 ms

banner-bot.png

banner-bot.png

142 ms

615120.jpg

615120.jpg

146 ms

126054.jpg

126054.jpg

198 ms

9830650.jpg

9830650.jpg

200 ms

3735911.jpg

3735911.jpg

325 ms

footer-wrap-blue.png

footer-wrap-blue.png

202 ms

MYWJ4lYm5dbZ1UBuYox79D8E0i7KZn-EPnyo3HZu7kw.woff

MYWJ4lYm5dbZ1UBuYox79D8E0i7KZn-EPnyo3HZu7kw.woff

69 ms

control_icons.gif

control_icons.gif

63 ms

loading.gif

loading.gif

63 ms

7529055_orig.jpg

7529055_orig.jpg

261 ms

7187923_orig.jpg

7187923_orig.jpg

195 ms

Accessibility Review

standwithmike.org accessibility score

90

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

Links do not have a discernible name

Best Practices

standwithmike.org 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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

standwithmike.org SEO score

88

Search Engine Optimization Advices

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

    N/A

  • Encoding

    UTF-8

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

standwithmike.org

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