Tools & Wizards About Us
straightspeak.com screenshot

Report Summary

  • 51

    Performance

    Renders faster than
    69% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 76

    SEO

    Google-friendlier than
    35% of websites

straightspeak.com

David Hughes | Straightspeak | Insight | Thought | Reflect

Page Load Speed

4.6 sec in total

First Response

634 ms

Resources Loaded

2.4 sec

Page Rendered

1.6 sec

straightspeak.com screenshot

About Website

Click here to check amazing Straightspeak content. Otherwise, check out these important facts you probably never knew about straightspeak.com

Visit straightspeak.com

Key Findings

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

Performance Metrics

straightspeak.com performance score

51

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

42/100

10%

LCP (Largest Contentful Paint)

Value13.6 s

0/100

25%

SI (Speed Index)

Value8.9 s

15/100

10%

TBT (Total Blocking Time)

Value150 ms

94/100

30%

CLS (Cumulative Layout Shift)

Value0.014

100/100

15%

TTI (Time to Interactive)

Value11.6 s

18/100

10%

Network Requests Diagram

straightspeak.com

634 ms

wp-emoji-release.min.js

50 ms

styles.css

92 ms

style.css

97 ms

e730c0fd04b0366c2ce977be31af60ff.min.css

242 ms

Our browser made a total of 90 requests to load all elements on the main page. We found that all of those requests were addressed to Straightspeak.com and no external sources were called. The less responsive or slowest element that took the longest time to load (634 ms) belongs to the original domain Straightspeak.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 701.2 kB (15%)

Content Size

4.7 MB

After Optimization

4.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Straightspeak.com main page is 4.7 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. 50% of websites need less resources to load. Images take 4.1 MB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 90.8 kB

  • Original 123.3 kB
  • After minification 119.7 kB
  • After compression 32.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 90.8 kB or 74% of the original size.

Image Optimization

-13%

Potential reduce by 536.0 kB

  • Original 4.1 MB
  • After minification 3.6 MB

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, Straightspeak needs image optimization as it can save up to 536.0 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-12%

Potential reduce by 24.2 kB

  • Original 195.2 kB
  • After minification 195.2 kB
  • After compression 171.0 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 24.2 kB or 12% of the original size.

CSS Optimization

-25%

Potential reduce by 50.2 kB

  • Original 199.3 kB
  • After minification 199.0 kB
  • After compression 149.1 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. Straightspeak.com needs all CSS files to be minified and compressed as it can save up to 50.2 kB or 25% of the original size.

Requests Breakdown

Number of requests can be reduced by 67 (76%)

Requests Now

88

After Optimization

21

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

straightspeak.com

straightspeak.com

634 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

50 ms

styles.css

styles.css

92 ms

style.css

style.css

97 ms

e730c0fd04b0366c2ce977be31af60ff.min.css

e730c0fd04b0366c2ce977be31af60ff.min.css

242 ms

cookies.js

cookies.js

134 ms

jquery.min.js

jquery.min.js

173 ms

jquery-migrate.min.js

jquery-migrate.min.js

136 ms

style.min.css

style.min.css

145 ms

theme.min.css

theme.min.css

145 ms

wp-embed.min.js

wp-embed.min.js

170 ms

modernizr.js

modernizr.js

170 ms

fusion-column-bg-image.js

fusion-column-bg-image.js

187 ms

cssua.js

cssua.js

185 ms

jquery.waypoints.js

jquery.waypoints.js

206 ms

fusion-waypoints.js

fusion-waypoints.js

211 ms

fusion-animations.js

fusion-animations.js

209 ms

fusion.js

fusion.js

225 ms

isotope.js

isotope.js

366 ms

packery.js

packery.js

367 ms

bootstrap.transition.js

bootstrap.transition.js

367 ms

bootstrap.tooltip.js

bootstrap.tooltip.js

368 ms

jquery.requestAnimationFrame.js

jquery.requestAnimationFrame.js

369 ms

jquery.easing.js

jquery.easing.js

370 ms

jquery.fitvids.js

jquery.fitvids.js

369 ms

jquery.flexslider.js

jquery.flexslider.js

370 ms

jquery.hoverflow.js

jquery.hoverflow.js

371 ms

jquery.hoverintent.js

jquery.hoverintent.js

371 ms

jquery.ilightbox.js

jquery.ilightbox.js

375 ms

jquery.infinitescroll.js

jquery.infinitescroll.js

373 ms

jquery.mousewheel.js

jquery.mousewheel.js

371 ms

jquery.placeholder.js

jquery.placeholder.js

371 ms

jquery.fade.js

jquery.fade.js

372 ms

imagesLoaded.js

imagesLoaded.js

373 ms

fusion-equal-heights.js

fusion-equal-heights.js

375 ms

fusion-parallax.js

fusion-parallax.js

384 ms

fusion-video-general.js

fusion-video-general.js

383 ms

fusion-video-bg.js

fusion-video-bg.js

345 ms

fusion-lightbox.js

fusion-lightbox.js

305 ms

fusion-tooltip.js

fusion-tooltip.js

300 ms

fusion-sharing-box.js

fusion-sharing-box.js

340 ms

jquery.sticky-kit.js

jquery.sticky-kit.js

338 ms

vimeoPlayer.js

vimeoPlayer.js

324 ms

avada-skip-link-focus-fix.js

avada-skip-link-focus-fix.js

323 ms

avada-general-footer.js

avada-general-footer.js

303 ms

avada-quantity.js

avada-quantity.js

299 ms

avada-crossfade-images.js

avada-crossfade-images.js

300 ms

avada-select.js

avada-select.js

285 ms

avada-tabs-widget.js

avada-tabs-widget.js

284 ms

jquery.elasticslider.js

jquery.elasticslider.js

265 ms

avada-live-search.js

avada-live-search.js

263 ms

fusion-alert.js

fusion-alert.js

260 ms

fusion-flexslider.js

fusion-flexslider.js

285 ms

fusion-blog.js

fusion-blog.js

144 ms

fusion-container.js

fusion-container.js

145 ms

avada-elastic-slider.js

avada-elastic-slider.js

176 ms

avada-fade.js

avada-fade.js

145 ms

avada-drop-down.js

avada-drop-down.js

151 ms

avada-to-top.js

avada-to-top.js

143 ms

avada-header.js

avada-header.js

158 ms

avada-menu.js

avada-menu.js

167 ms

avada-sidebars.js

avada-sidebars.js

167 ms

bootstrap.scrollspy.js

bootstrap.scrollspy.js

169 ms

avada-scrollspy.js

avada-scrollspy.js

177 ms

fusion-responsive-typography.js

fusion-responsive-typography.js

196 ms

fusion-scroll-to-anchor.js

fusion-scroll-to-anchor.js

210 ms

fusion-general-global.js

fusion-general-global.js

210 ms

fusion-vertical-menu-widget.js

fusion-vertical-menu-widget.js

200 ms

fusion-video.js

fusion-video.js

205 ms

fusion-column.js

fusion-column.js

216 ms

icomoon.woff

icomoon.woff

270 ms

pattern9.png

pattern9.png

267 ms

straightspeak_smlno2_tag6.jpg

straightspeak_smlno2_tag6.jpg

268 ms

Screen-Shot-2022-04-26-at-9.41.32-AM-e1650984586374.png

Screen-Shot-2022-04-26-at-9.41.32-AM-e1650984586374.png

402 ms

Tucker-montage-Screen-Shot-2022-05-02-at-9.40.51-AM-1-1024x655.png

Tucker-montage-Screen-Shot-2022-05-02-at-9.40.51-AM-1-1024x655.png

421 ms

Tuckers-mouth-Screen-Shot-2022-05-02-at-1.35.31-PM-copy-1-300x214.png

Tuckers-mouth-Screen-Shot-2022-05-02-at-1.35.31-PM-copy-1-300x214.png

213 ms

Supreme-Ct.-Screen-Shot-2022-05-05-at-10.29.01-AM.png

Supreme-Ct.-Screen-Shot-2022-05-05-at-10.29.01-AM.png

315 ms

Bk-cvr-Screen-Shot-2022-04-30-at-2.39.16-PM-copy-201x300.png

Bk-cvr-Screen-Shot-2022-04-30-at-2.39.16-PM-copy-201x300.png

243 ms

Truth-2-Screen-Shot-2022-04-26-at-9.36.45-AM-copy-2-e1650986310279.png

Truth-2-Screen-Shot-2022-04-26-at-9.36.45-AM-copy-2-e1650986310279.png

256 ms

Shoes-Screen-Shot-2022-05-05-at-5.49.29-PM-copy-257x300.png

Shoes-Screen-Shot-2022-05-05-at-5.49.29-PM-copy-257x300.png

309 ms

Montage-final-Screen-Shot-2022-04-02-at-11.55.41-AM-e1649604021220.png

Montage-final-Screen-Shot-2022-04-02-at-11.55.41-AM-e1649604021220.png

424 ms

Feature-Screen-Shot-2020-11-22-at-8.33.14-AM-copy.png

Feature-Screen-Shot-2020-11-22-at-8.33.14-AM-copy.png

302 ms

897a.png

897a.png

340 ms

cw4.png

cw4.png

351 ms

tw4.png

tw4.png

351 ms

Screen-Shot-2022-04-26-at-9.41.32-AM-66x66.png

Screen-Shot-2022-04-26-at-9.41.32-AM-66x66.png

359 ms

Montage-final-Screen-Shot-2022-04-02-at-11.55.41-AM-66x66.png

Montage-final-Screen-Shot-2022-04-02-at-11.55.41-AM-66x66.png

378 ms

Feature-Screen-Shot-2020-11-22-at-8.33.14-AM-copy-66x66.png

Feature-Screen-Shot-2020-11-22-at-8.33.14-AM-copy-66x66.png

345 ms

4-Gen-1-copy1.gif

4-Gen-1-copy1.gif

379 ms

StraightSpeak_Reva.png

StraightSpeak_Reva.png

352 ms

Accessibility Review

straightspeak.com accessibility score

93

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

High

Links do not have a discernible name

Best Practices

straightspeak.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

straightspeak.com SEO score

76

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

    UTF-8

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

Social Sharing Optimization

straightspeak.com

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