Tools & Wizards About Us
getawesomesupport.com screenshot

Report Summary

  • 12

    Performance

    Renders faster than
    25% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

getawesomesupport.com

Awesome Support: The Best Helpdesk and Support Plugin For WordPress

Page Load Speed

4.1 sec in total

First Response

67 ms

Resources Loaded

3.5 sec

Page Rendered

543 ms

getawesomesupport.com screenshot

About Website

Click here to check amazing Get Awesome Support content for Sweden. Otherwise, check out these important facts you probably never knew about getawesomesupport.com

Awesome Support is the most versatile and feature-rich help-desk plugin for WordPress. Get started for free and add premium features as your business grows.

Visit getawesomesupport.com

Key Findings

We analyzed Getawesomesupport.com page load time and found that the first response time was 67 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

getawesomesupport.com performance score

12

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.2 s

3/100

10%

LCP (Largest Contentful Paint)

Value9.8 s

0/100

25%

SI (Speed Index)

Value12.5 s

3/100

10%

TBT (Total Blocking Time)

Value2,910 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.176

68/100

15%

TTI (Time to Interactive)

Value22.4 s

1/100

10%

Network Requests Diagram

getawesomesupport.com

67 ms

analytics.js

25 ms

shortcodes.css

13 ms

font-awesome.min.css

24 ms

fontello.css

39 ms

Our browser made a total of 138 requests to load all elements on the main page. We found that 67% of them (93 requests) were addressed to the original Getawesomesupport.com, 15% (21 requests) were made to Fonts.gstatic.com and 8% (11 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (810 ms) relates to the external source Fonts.gstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 193.9 kB (20%)

Content Size

963.4 kB

After Optimization

769.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Getawesomesupport.com main page is 963.4 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. Only a small number of websites need less resources to load. Javascripts take 377.0 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 127.5 kB

  • Original 152.5 kB
  • After minification 140.5 kB
  • After compression 25.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 127.5 kB or 84% of the original size.

Image Optimization

-12%

Potential reduce by 26.3 kB

  • Original 227.3 kB
  • After minification 201.0 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, Get Awesome Support needs image optimization as it can save up to 26.3 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-6%

Potential reduce by 23.0 kB

  • Original 377.0 kB
  • After minification 377.0 kB
  • After compression 354.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. This website has mostly compressed JavaScripts.

CSS Optimization

-8%

Potential reduce by 17.1 kB

  • Original 206.6 kB
  • After minification 206.6 kB
  • After compression 189.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. Getawesomesupport.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 94 (85%)

Requests Now

110

After Optimization

16

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

getawesomesupport.com

getawesomesupport.com

67 ms

analytics.js

analytics.js

25 ms

shortcodes.css

shortcodes.css

13 ms

font-awesome.min.css

font-awesome.min.css

24 ms

fontello.css

fontello.css

39 ms

magnific-popup.css

magnific-popup.css

38 ms

admin-popup.css

admin-popup.css

37 ms

acknowledge.css

acknowledge.css

37 ms

forms.min.css

forms.min.css

37 ms

styles.css

styles.css

36 ms

edd.min.css

edd.min.css

50 ms

style_login_widget.css

style_login_widget.css

51 ms

customfaq.css

customfaq.css

49 ms

faq.css

faq.css

47 ms

coh-styles.css

coh-styles.css

47 ms

style.css

style.css

51 ms

dashicons.min.css

dashicons.min.css

64 ms

thickbox.css

thickbox.css

52 ms

as-documentation.css

as-documentation.css

52 ms

css

css

51 ms

css

css

120 ms

styles.css

styles.css

56 ms

style.dev.css

style.dev.css

83 ms

style.css

style.css

77 ms

style.css

style.css

78 ms

css

css

70 ms

tablepress-combined.min.css

tablepress-combined.min.css

79 ms

edd-jilt-frontend.min.css

edd-jilt-frontend.min.css

80 ms

private-credentials.css

private-credentials.css

79 ms

shortcodes_responsive.css

shortcodes_responsive.css

105 ms

magnific_popup.css

magnific_popup.css

107 ms

style.css

style.css

106 ms

style.css

style.css

107 ms

colorbox.css

colorbox.css

109 ms

style.css

style.css

110 ms

style.css

style.css

111 ms

n2-custom.css

n2-custom.css

112 ms

edd-etd.css

edd-etd.css

112 ms

jquery.js

jquery.js

113 ms

shortcodes.js

shortcodes.js

114 ms

40 ms

jilt.js

jilt.js

37 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

111 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

126 ms

jquery.magnific-popup.min.js

jquery.magnific-popup.min.js

114 ms

ec.js

ec.js

12 ms

admin-popup.js

admin-popup.js

103 ms

frontend.min.js

frontend.min.js

104 ms

jquery.validate.min.js

jquery.validate.min.js

104 ms

additional-methods.js

additional-methods.js

106 ms

jquery.cookie.min.js

jquery.cookie.min.js

107 ms

tracking.min.js

tracking.min.js

107 ms

collect

collect

19 ms

collect

collect

32 ms

functions.js

functions.js

99 ms

underscore.min.js

underscore.min.js

99 ms

wp-util.min.js

wp-util.min.js

99 ms

script.js

script.js

101 ms

jquery.zoom.min.js

jquery.zoom.min.js

99 ms

jquery.colorbox-min.js

jquery.colorbox-min.js

124 ms

imagesloaded.pkgd.min.js

imagesloaded.pkgd.min.js

121 ms

script.js

script.js

123 ms

edd-etd.min.js

edd-etd.min.js

119 ms

js

js

175 ms

frontend-builder-global-functions.js

frontend-builder-global-functions.js

169 ms

scripts.js

scripts.js

155 ms

edd-ajax.min.js

edd-ajax.min.js

155 ms

customfaq.js

customfaq.js

155 ms

customfaq-live-search.js

customfaq-live-search.js

174 ms

faq.js

faq.js

175 ms

faq-live-search.js

faq-live-search.js

151 ms

thickbox.js

thickbox.js

150 ms

sidebar.js

sidebar.js

148 ms

as-documentation.js

as-documentation.js

148 ms

as-documentation-live-search.js

as-documentation-live-search.js

147 ms

jquery.mobile.custom.min.js

jquery.mobile.custom.min.js

147 ms

custom.js

custom.js

146 ms

private-credentials.js

private-credentials.js

145 ms

jquery.fitvids.js

jquery.fitvids.js

144 ms

waypoints.min.js

waypoints.min.js

143 ms

jquery.magnific-popup.js

jquery.magnific-popup.js

144 ms

frontend-builder-scripts.js

frontend-builder-scripts.js

145 ms

common.js

common.js

129 ms

core.min.js

core.min.js

127 ms

effect.min.js

effect.min.js

127 ms

effect-slide.min.js

effect-slide.min.js

126 ms

wp-embed.min.js

wp-embed.min.js

125 ms

jquery.easypiechart.js

jquery.easypiechart.js

124 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

123 ms

mediaelement-migrate.min.js

mediaelement-migrate.min.js

123 ms

wp-mediaelement.min.js

wp-mediaelement.min.js

123 ms

et_shortcodes_frontend.js

et_shortcodes_frontend.js

119 ms

salvattore.min.js

salvattore.min.js

119 ms

-SV-IUD6WvI

-SV-IUD6WvI

216 ms

Me5g3uEEDVE

Me5g3uEEDVE

296 ms

fbevents.js

fbevents.js

432 ms

uwt.js

uwt.js

433 ms

script.js

script.js

502 ms

awsome_support_grayscale_logo-1.png

awsome_support_grayscale_logo-1.png

174 ms

AS-AdminReportingWidgets-05.jpg

AS-AdminReportingWidgets-05.jpg

263 ms

6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7gujVj9w.ttf

6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7gujVj9w.ttf

396 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zwlxdr3cOWxw.ttf

6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zwlxdr3cOWxw.ttf

480 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3i94_wlxdr3cOWxw.ttf

6xKydSBYKcSV-LCoeQqfX1RYOo3i94_wlxdr3cOWxw.ttf

481 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwlxdr3cOWxw.ttf

6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwlxdr3cOWxw.ttf

412 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwlxdr3cOWxw.ttf

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwlxdr3cOWxw.ttf

477 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3iu4nwlxdr3cOWxw.ttf

6xKydSBYKcSV-LCoeQqfX1RYOo3iu4nwlxdr3cOWxw.ttf

479 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrQVIT9d4cw.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrQVIT9d4cw.ttf

319 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCIPrQVIT9d4cw.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCIPrQVIT9d4cw.ttf

809 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCIPrQVIT9d4cw.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCIPrQVIT9d4cw.ttf

392 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCIPrQVIT9d4cw.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCIPrQVIT9d4cw.ttf

317 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCIPrQVIT9d4cw.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCIPrQVIT9d4cw.ttf

425 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQVIT9d4cw.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQVIT9d4cw.ttf

365 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrQVIT9d4cw.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrQVIT9d4cw.ttf

640 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaorCIPrQVIT9d4cw.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaorCIPrQVIT9d4cw.ttf

643 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao7CIPrQVIT9d4cw.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao7CIPrQVIT9d4cw.ttf

810 ms

modules.ttf

modules.ttf

242 ms

www-player.css

www-player.css

198 ms

www-embed-player.js

www-embed-player.js

199 ms

base.js

base.js

199 ms

S6u9w4BMUTPHh6UVSwiPHA3q5d0.ttf

S6u9w4BMUTPHh6UVSwiPHA3q5d0.ttf

332 ms

S6u9w4BMUTPHh50XSwiPHA3q5d0.ttf

S6u9w4BMUTPHh50XSwiPHA3q5d0.ttf

333 ms

S6uyw4BMUTPHjx4wWyWtFCc.ttf

S6uyw4BMUTPHjx4wWyWtFCc.ttf

546 ms

S6uyw4BMUTPHjxAwWyWtFCc.ttf

S6uyw4BMUTPHjxAwWyWtFCc.ttf

547 ms

S6u9w4BMUTPHh7USSwiPHA3q5d0.ttf

S6u9w4BMUTPHh7USSwiPHA3q5d0.ttf

546 ms

S6u8w4BMUTPHh30AXC-vNiXg7Q.ttf

S6u8w4BMUTPHh30AXC-vNiXg7Q.ttf

549 ms

lazyload-8.5.2.min.js

lazyload-8.5.2.min.js

206 ms

loadingAnimation.gif

loadingAnimation.gif

108 ms

base.js

base.js

3 ms

-SV-IUD6WvI

-SV-IUD6WvI

112 ms

Me5g3uEEDVE

Me5g3uEEDVE

161 ms

www-player.css

www-player.css

53 ms

www-embed-player.js

www-embed-player.js

77 ms

base.js

base.js

112 ms

198.png

198.png

446 ms

154.png

154.png

446 ms

159.png

159.png

447 ms

130.png

130.png

446 ms

25.png

25.png

447 ms

Accessibility Review

getawesomesupport.com accessibility score

80

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

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

getawesomesupport.com best practices score

75

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

getawesomesupport.com SEO score

93

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

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

    UTF-8

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

getawesomesupport.com

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