Tools & Wizards About Us
execute.io screenshot

Report Summary

  • 33

    Performance

    Renders faster than
    53% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

execute.io

TrafficScore Execute.io – Trust But Verify Your Digital Marketing

Page Load Speed

1.1 sec in total

First Response

39 ms

Resources Loaded

866 ms

Page Rendered

156 ms

execute.io screenshot

About Website

Welcome to execute.io homepage info - get ready to check Execute best content right away, or after learning these important things about execute.io

TrafficScore is an analytics plugin for your website that scores the quality of visitors from all sources.

Visit execute.io

Key Findings

We analyzed Execute.io page load time and found that the first response time was 39 ms and then it took 1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

execute.io performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

65/100

10%

LCP (Largest Contentful Paint)

Value9.0 s

1/100

25%

SI (Speed Index)

Value10.3 s

8/100

10%

TBT (Total Blocking Time)

Value970 ms

28/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value11.0 s

21/100

10%

Network Requests Diagram

execute.io

39 ms

execute.io

66 ms

normalize.css

18 ms

font-awesome.min.css

19 ms

materialize.min.css

30 ms

Our browser made a total of 84 requests to load all elements on the main page. We found that 93% of them (78 requests) were addressed to the original Execute.io, 2% (2 requests) were made to Cdn.dealerx.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (513 ms) relates to the external source Cdn.segment.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 243.1 kB (26%)

Content Size

919.9 kB

After Optimization

676.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Execute.io main page is 919.9 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. 70% of websites need less resources to load. Javascripts take 339.7 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 89.0 kB

  • Original 109.3 kB
  • After minification 99.1 kB
  • After compression 20.2 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 89.0 kB or 81% of the original size.

Image Optimization

-41%

Potential reduce by 136.6 kB

  • Original 330.3 kB
  • After minification 193.8 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, Execute needs image optimization as it can save up to 136.6 kB or 41% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-1%

Potential reduce by 5.1 kB

  • Original 339.7 kB
  • After minification 339.3 kB
  • After compression 334.6 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

-9%

Potential reduce by 12.4 kB

  • Original 140.6 kB
  • After minification 140.5 kB
  • After compression 128.2 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. Execute.io has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 71 (92%)

Requests Now

77

After Optimization

6

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

execute.io

execute.io

39 ms

execute.io

execute.io

66 ms

normalize.css

normalize.css

18 ms

font-awesome.min.css

font-awesome.min.css

19 ms

materialize.min.css

materialize.min.css

30 ms

bootstrap.css

bootstrap.css

54 ms

animate.min.css

animate.min.css

42 ms

sweet-alert.css

sweet-alert.css

22 ms

owl.carousel.css

owl.carousel.css

24 ms

owl.transitions.css

owl.transitions.css

24 ms

owl.theme.css

owl.theme.css

39 ms

main.css

main.css

44 ms

responsive.css

responsive.css

48 ms

style.min.css

style.min.css

75 ms

buttons.min.css

buttons.min.css

48 ms

dashicons.min.css

dashicons.min.css

71 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

45 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

46 ms

media-views.min.css

media-views.min.css

81 ms

imgareaselect.css

imgareaselect.css

69 ms

jquery.min.js

jquery.min.js

88 ms

jquery-migrate.min.js

jquery-migrate.min.js

86 ms

workflow.bundle.js

workflow.bundle.js

86 ms

utils.min.js

utils.min.js

106 ms

moxie.min.js

moxie.min.js

110 ms

plupload.min.js

plupload.min.js

86 ms

jquery.min.js

jquery.min.js

124 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

101 ms

detectmobilebrowser.js

detectmobilebrowser.js

102 ms

isotope.pkgd.min.js

isotope.pkgd.min.js

105 ms

wow.min.js

wow.min.js

102 ms

waypoints.js

waypoints.js

103 ms

waypointb.js

waypointb.js

106 ms

noframework.js

noframework.js

106 ms

group.js

group.js

104 ms

context.js

context.js

106 ms

inview.js

inview.js

121 ms

jquery.counterup.min.js

jquery.counterup.min.js

134 ms

jquery.nicescroll.min.js

jquery.nicescroll.min.js

134 ms

owl.carousel.min.js

owl.carousel.min.js

128 ms

materialize.min.js

materialize.min.js

133 ms

sweet-alert.min.js

sweet-alert.min.js

125 ms

common.js

common.js

123 ms

main.js

main.js

109 ms

TweenLite.min.js

TweenLite.min.js

106 ms

EasePack.min.js

EasePack.min.js

109 ms

particles.js

particles.js

105 ms

underscore.min.js

underscore.min.js

104 ms

shortcode.min.js

shortcode.min.js

104 ms

backbone.min.js

backbone.min.js

104 ms

wp-util.min.js

wp-util.min.js

82 ms

wp-backbone.min.js

wp-backbone.min.js

128 ms

media-models.min.js

media-models.min.js

125 ms

wp-plupload.min.js

wp-plupload.min.js

120 ms

core.min.js

core.min.js

118 ms

mouse.min.js

mouse.min.js

117 ms

sortable.min.js

sortable.min.js

117 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

122 ms

mediaelement-migrate.min.js

mediaelement-migrate.min.js

120 ms

wp-mediaelement.min.js

wp-mediaelement.min.js

121 ms

api-request.min.js

api-request.min.js

121 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

121 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

122 ms

wp-polyfill.min.js

wp-polyfill.min.js

125 ms

dom-ready.min.js

dom-ready.min.js

123 ms

hooks.min.js

hooks.min.js

121 ms

i18n.min.js

i18n.min.js

122 ms

a11y.min.js

a11y.min.js

120 ms

clipboard.min.js

clipboard.min.js

122 ms

callout.jpg

callout.jpg

302 ms

media-views.min.js

media-views.min.js

114 ms

ts.png

ts.png

388 ms

media-editor.min.js

media-editor.min.js

112 ms

media-audiovideo.min.js

media-audiovideo.min.js

99 ms

logo.png

logo.png

116 ms

Roboto-Thin.ttf

Roboto-Thin.ttf

114 ms

Roboto-Light.ttf

Roboto-Light.ttf

114 ms

Roboto-Regular.ttf

Roboto-Regular.ttf

113 ms

Roboto-Medium.ttf

Roboto-Medium.ttf

90 ms

Roboto-Bold.ttf

Roboto-Bold.ttf

113 ms

analytics.js

analytics.js

52 ms

analytics.min.js

analytics.min.js

513 ms

collect

collect

16 ms

js

js

66 ms

Accessibility Review

execute.io accessibility score

73

Accessibility Issues

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

Image elements do not have [alt] attributes

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

execute.io 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

execute.io SEO score

92

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

Image elements do not have [alt] attributes

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

    N/A

  • Encoding

    UTF-8

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

execute.io

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