Tools & Wizards About Us
gstarcad.my screenshot

Report Summary

  • 0

    Performance

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

gstarcad.my

GstarCAD 2024 - SEAMLESS EXPERIENCE WITH HIGH COMPATIBILITY

Page Load Speed

17.2 sec in total

First Response

1.2 sec

Resources Loaded

14.6 sec

Page Rendered

1.4 sec

gstarcad.my screenshot

About Website

Welcome to gstarcad.my homepage info - get ready to check GstarCAD best content right away, or after learning these important things about gstarcad.my

GSTARCAD 2024 with accelerated performance, enhanced compatibility and elevated user experience, GstarCAD 2024 boosts design productivity.

Visit gstarcad.my

Key Findings

We analyzed Gstarcad.my page load time and found that the first response time was 1.2 sec and then it took 16 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.

Performance Metrics

gstarcad.my performance score

0

Network Requests Diagram

gstarcad.my

1191 ms

www.neofame.com.my

2296 ms

font-awesome.min.css

26 ms

standalone.c994e3b5bb14b9bef74f81d0a96db5621456459599.css

1069 ms

jquery.min.js

32 ms

Our browser made a total of 94 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Gstarcad.my, 37% (35 requests) were made to Maps.googleapis.com and 27% (25 requests) were made to Neofame.com.my. The less responsive or slowest element that took the longest time to load (8 sec) relates to the external source Neofame.com.my.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.0 MB (40%)

Content Size

2.6 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Gstarcad.my main page is 2.6 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. 65% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 166.7 kB

  • Original 193.1 kB
  • After minification 152.7 kB
  • After compression 26.4 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 40.5 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 166.7 kB or 86% of the original size.

Image Optimization

-3%

Potential reduce by 37.9 kB

  • Original 1.2 MB
  • After minification 1.2 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. GstarCAD images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 498.7 kB

  • Original 749.0 kB
  • After minification 749.0 kB
  • After compression 250.3 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 498.7 kB or 67% of the original size.

CSS Optimization

-84%

Potential reduce by 305.8 kB

  • Original 362.0 kB
  • After minification 327.7 kB
  • After compression 56.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. Gstarcad.my needs all CSS files to be minified and compressed as it can save up to 305.8 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 21 (26%)

Requests Now

82

After Optimization

61

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

gstarcad.my

gstarcad.my

1191 ms

www.neofame.com.my

www.neofame.com.my

2296 ms

font-awesome.min.css

font-awesome.min.css

26 ms

standalone.c994e3b5bb14b9bef74f81d0a96db5621456459599.css

standalone.c994e3b5bb14b9bef74f81d0a96db5621456459599.css

1069 ms

jquery.min.js

jquery.min.js

32 ms

jquery-ui.min.js

jquery-ui.min.js

37 ms

scripts-aa29b0eaa2ee66a667ca31394e5973511456459599.js

scripts-aa29b0eaa2ee66a667ca31394e5973511456459599.js

1985 ms

js

js

60 ms

analytics.js

analytics.js

108 ms

ajax_loader.svg

ajax_loader.svg

261 ms

logo-mini.png

logo-mini.png

272 ms

index.php

index.php

777 ms

nt-03_04u9-wh.png

nt-03_04u9-wh.png

814 ms

gstarcad2016-min.jpg

gstarcad2016-min.jpg

3206 ms

lumion_6-min.jpg

lumion_6-min.jpg

3801 ms

keyshot_6-min.jpg

keyshot_6-min.jpg

2914 ms

categories-01_gstarcad2015_ymd1-4r.png

categories-01_gstarcad2015_ymd1-4r.png

1323 ms

categories-02_machanical2015_78wg-b0.png

categories-02_machanical2015_78wg-b0.png

2798 ms

categories-06_mobileclient_qm4o-3o.png

categories-06_mobileclient_qm4o-3o.png

1773 ms

categories-03_lumion_dgt6-fb.png

categories-03_lumion_dgt6-fb.png

3025 ms

categories-04_mylumion_2nu3-qv.png

categories-04_mylumion_2nu3-qv.png

2416 ms

categories-05_keyshot_d58g-l5.png

categories-05_keyshot_d58g-l5.png

3046 ms

G2016_2.png

G2016_2.png

4337 ms

g2016-ribbon.png

g2016-ribbon.png

4657 ms

g2016-classic.png

g2016-classic.png

4950 ms

Lumion6PreviewPic-min.jpg

Lumion6PreviewPic-min.jpg

4083 ms

LumionLogo.png

LumionLogo.png

4918 ms

keyshot-6-home-min.jpg

keyshot-6-home-min.jpg

5899 ms

How-its-different-materials1.png

How-its-different-materials1.png

7974 ms

training_room2b-min.jpg

training_room2b-min.jpg

6492 ms

cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff

cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff

47 ms

uYKcPVoh6c5R0NpdEY5A-Q.woff

uYKcPVoh6c5R0NpdEY5A-Q.woff

47 ms

MTP_ySUJH_bn48VBG8sNShsxEYwM7FgeyaSgU71cLG0.woff

MTP_ySUJH_bn48VBG8sNShsxEYwM7FgeyaSgU71cLG0.woff

65 ms

k3k702ZOKiLJc3WVjuplzBsxEYwM7FgeyaSgU71cLG0.woff

k3k702ZOKiLJc3WVjuplzBsxEYwM7FgeyaSgU71cLG0.woff

66 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

32 ms

glyphs.woff

glyphs.woff

4872 ms

collect

collect

33 ms

collect

collect

61 ms

sdk.js

sdk.js

58 ms

132 ms

xd_arbiter.php

xd_arbiter.php

25 ms

common.js

common.js

6 ms

util.js

util.js

27 ms

stats.js

stats.js

48 ms

AuthenticationService.Authenticate

AuthenticationService.Authenticate

421 ms

map.js

map.js

38 ms

marker.js

marker.js

37 ms

like.php

like.php

134 ms

like.php

like.php

286 ms

onion.js

onion.js

26 ms

openhand_8_8.cur

openhand_8_8.cur

92 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

226 ms

controls.js

controls.js

54 ms

TY3MhkXpWJ-.js

TY3MhkXpWJ-.js

334 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

319 ms

spotlight-poi.png

spotlight-poi.png

314 ms

css

css

355 ms

transparent.png

transparent.png

317 ms

google4.png

google4.png

251 ms

mapcnt6.png

mapcnt6.png

260 ms

sv5.png

sv5.png

260 ms

tmapctrl.png

tmapctrl.png

66 ms

cb_scout5.png

cb_scout5.png

67 ms

tmapctrl4.png

tmapctrl4.png

115 ms

imgs8.png

imgs8.png

73 ms

vt

vt

105 ms

vt

vt

218 ms

vt

vt

121 ms

vt

vt

126 ms

vt

vt

127 ms

vt

vt

124 ms

vt

vt

127 ms

vt

vt

193 ms

vt

vt

194 ms

vt

vt

193 ms

vt

vt

195 ms

vt

vt

195 ms

vt

vt

224 ms

vt

vt

227 ms

vt

vt

257 ms

vt

vt

221 ms

vt

vt

239 ms

vt

vt

236 ms

vt

vt

284 ms

vt

vt

261 ms

vt

vt

285 ms

vt

vt

281 ms

vt

vt

304 ms

vt

vt

313 ms

vt

vt

311 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

11 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

50 ms

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

50 ms

d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf

d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf

51 ms

Accessibility Review

gstarcad.my accessibility score

82

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

Buttons do not have an accessible name

High

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

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

Best Practices

gstarcad.my best practices score

83

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

SEO Factors

gstarcad.my SEO score

93

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

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 Gstarcad.my 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 Gstarcad.my 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

gstarcad.my

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