Tools & Wizards About Us
gcode.ws screenshot

Report Summary

  • 47

    Performance

    Renders faster than
    65% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 71

    SEO

    Google-friendlier than
    30% of websites

gcode.ws

gcode viewer - online gcode viewer and analyzer in your browser!

Page Load Speed

1.1 sec in total

First Response

79 ms

Resources Loaded

914 ms

Page Rendered

107 ms

gcode.ws screenshot

About Website

Welcome to gcode.ws homepage info - get ready to check Gcode best content for United States right away, or after learning these important things about gcode.ws

Visual GCode viewer and analyzer in your browser. No need to upload you GCode anywhere, everything is done locally.

Visit gcode.ws

Key Findings

We analyzed Gcode.ws page load time and found that the first response time was 79 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

gcode.ws performance score

47

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

27/100

10%

LCP (Largest Contentful Paint)

Value4.6 s

35/100

25%

SI (Speed Index)

Value3.8 s

83/100

10%

TBT (Total Blocking Time)

Value660 ms

45/100

30%

CLS (Cumulative Layout Shift)

Value0.141

78/100

15%

TTI (Time to Interactive)

Value10.6 s

23/100

10%

Network Requests Diagram

gcode.ws

79 ms

gcode.ws

41 ms

jquery-ui-1.9.0.custom.css

14 ms

bootstrap.css

37 ms

codemirror.css

17 ms

Our browser made a total of 39 requests to load all elements on the main page. We found that 56% of them (22 requests) were addressed to the original Gcode.ws, 15% (6 requests) were made to Apis.google.com and 8% (3 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (369 ms) relates to the external source Developers.google.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 40.4 kB (17%)

Content Size

237.6 kB

After Optimization

197.2 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Gcode.ws main page is 237.6 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. 65% of websites need less resources to load. Javascripts take 169.5 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 17.7 kB

  • Original 22.9 kB
  • After minification 18.0 kB
  • After compression 5.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. This page needs HTML code to be minified as it can gain 4.9 kB, which is 21% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 17.7 kB or 77% of the original size.

Image Optimization

-49%

Potential reduce by 22.2 kB

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

JavaScript Optimization

-0%

Potential reduce by 449 B

  • Original 169.5 kB
  • After minification 169.5 kB
  • After compression 169.1 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.

Requests Breakdown

Number of requests can be reduced by 27 (77%)

Requests Now

35

After Optimization

8

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

gcode.ws

gcode.ws

79 ms

gcode.ws

gcode.ws

41 ms

jquery-ui-1.9.0.custom.css

jquery-ui-1.9.0.custom.css

14 ms

bootstrap.css

bootstrap.css

37 ms

codemirror.css

codemirror.css

17 ms

style.css

style.css

18 ms

jquery-1.8.2.js

jquery-1.8.2.js

35 ms

jquery-ui-1.9.0.custom.js

jquery-ui-1.9.0.custom.js

73 ms

codemirror.js

codemirror.js

70 ms

gcode_mode.js

gcode_mode.js

27 ms

three.js

three.js

66 ms

bootstrap.js

bootstrap.js

65 ms

modernizr.custom.09684.js

modernizr.custom.09684.js

69 ms

TrackballControls.js

TrackballControls.js

70 ms

zlib.min.js

zlib.min.js

66 ms

ui.js

ui.js

70 ms

gCodeReader.js

gCodeReader.js

145 ms

renderer.js

renderer.js

147 ms

analyzer.js

analyzer.js

147 ms

renderer3d.js

renderer3d.js

150 ms

background.jpg

background.jpg

87 ms

ga.js

ga.js

46 ms

all.js

all.js

42 ms

widgets.js

widgets.js

288 ms

plusone.js

plusone.js

90 ms

logo.png

logo.png

35 ms

all.js

all.js

24 ms

__utm.gif

__utm.gif

40 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

17 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

37 ms

fastbutton

fastbutton

31 ms

postmessageRelay

postmessageRelay

71 ms

developers.google.com

developers.google.com

369 ms

544727282-postmessagerelay.js

544727282-postmessagerelay.js

25 ms

rpc:shindig_random.js

rpc:shindig_random.js

14 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

29 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

156 ms

settings

settings

105 ms

button.856debeac157d9669cf51e73a08fbc93.js

button.856debeac157d9669cf51e73a08fbc93.js

68 ms

Accessibility Review

gcode.ws accessibility score

77

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Form elements do not have associated labels

Best Practices

gcode.ws best practices score

67

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

Missing source maps for large first-party JavaScript

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

gcode.ws SEO score

71

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

robots.txt is not valid

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 Gcode.ws 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 Gcode.ws 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

gcode.ws

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