Tools & Wizards About Us
noblesim.com screenshot

Report Summary

  • 40

    Performance

    Renders faster than
    59% of other websites

  • 41

    Accessibility

    Visual factors better than
    that of 19% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 67

    SEO

    Google-friendlier than
    26% of websites

noblesim.com

??????? ???????? ??????? ?ҤҶ١ ???͡?????

Page Load Speed

12.4 sec in total

First Response

883 ms

Resources Loaded

10.6 sec

Page Rendered

955 ms

noblesim.com screenshot

About Website

Click here to check amazing Noblesim content for Thailand. Otherwise, check out these important facts you probably never knew about noblesim.com

??ԡ?? ???????? ??????? ???????Ѿ?????? ?????ѧ?? ????˧?? ???෾ ??????? 399 ?ҷ ?ӹ?????????Ѿ?? ?ٴǧ???????Ѿ?? ??????????????Ͷ?? ?????????Ѿ?? ???? ???ӡѴ noblesim.com

Visit noblesim.com

Key Findings

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

Performance Metrics

noblesim.com performance score

40

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

14/100

10%

LCP (Largest Contentful Paint)

Value4.9 s

29/100

25%

SI (Speed Index)

Value9.1 s

14/100

10%

TBT (Total Blocking Time)

Value720 ms

41/100

30%

CLS (Cumulative Layout Shift)

Value0.011

100/100

15%

TTI (Time to Interactive)

Value10.5 s

23/100

10%

Network Requests Diagram

noblesim.com

883 ms

home.php

753 ms

text.css

274 ms

js

58 ms

jquery-1.9.1.min.js

550 ms

Our browser made a total of 82 requests to load all elements on the main page. We found that 96% of them (79 requests) were addressed to the original Noblesim.com, 1% (1 request) were made to Googletagmanager.com and 1% (1 request) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (4.7 sec) belongs to the original domain Noblesim.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 771.4 kB (32%)

Content Size

2.4 MB

After Optimization

1.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-98%

Potential reduce by 702.7 kB

  • Original 718.6 kB
  • After minification 317.5 kB
  • After compression 15.9 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 401.2 kB, which is 56% 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 702.7 kB or 98% of the original size.

Image Optimization

-4%

Potential reduce by 63.0 kB

  • Original 1.6 MB
  • After minification 1.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. Noblesim images are well optimized though.

JavaScript Optimization

-13%

Potential reduce by 5.0 kB

  • Original 38.0 kB
  • After minification 38.0 kB
  • After compression 33.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 5.0 kB or 13% of the original size.

CSS Optimization

-32%

Potential reduce by 631 B

  • Original 2.0 kB
  • After minification 2.0 kB
  • After compression 1.4 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. Noblesim.com needs all CSS files to be minified and compressed as it can save up to 631 B or 32% of the original size.

Requests Breakdown

Number of requests can be reduced by 7 (9%)

Requests Now

77

After Optimization

70

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

noblesim.com

noblesim.com

883 ms

home.php

home.php

753 ms

text.css

text.css

274 ms

js

js

58 ms

jquery-1.9.1.min.js

jquery-1.9.1.min.js

550 ms

fbevents.js

fbevents.js

14 ms

bg.jpg

bg.jpg

1667 ms

logo.png

logo.png

560 ms

menu_01.png

menu_01.png

815 ms

menu_02.png

menu_02.png

834 ms

menu_03.png

menu_03.png

833 ms

menu_04.png

menu_04.png

836 ms

menu_05.png

menu_05.png

828 ms

shadow_topm.png

shadow_topm.png

1086 ms

text2.png

text2.png

1101 ms

header_02.png

header_02.png

2458 ms

header_04.png

header_04.png

1916 ms

header_06.png

header_06.png

3212 ms

qr.png

qr.png

1617 ms

addline.png

addline.png

3216 ms

bar_cate.png

bar_cate.png

1891 ms

bullet.png

bullet.png

1938 ms

line_sidemenu.png

line_sidemenu.png

2161 ms

bar_article.png

bar_article.png

2459 ms

icon_new.gif

icon_new.gif

2226 ms

icon_hot.gif

icon_hot.gif

2429 ms

tabien_home.gif

tabien_home.gif

2494 ms

ban_garantee.png

ban_garantee.png

2964 ms

dbd.jpg

dbd.jpg

2732 ms

side-pdtop.png

side-pdtop.png

2739 ms

side-pdfooter.png

side-pdfooter.png

2765 ms

img_search.png

img_search.png

3002 ms

bt_tumnine.png

bt_tumnine.png

3013 ms

about-content2.png

about-content2.png

3048 ms

about-footer.png

about-footer.png

3232 ms

line_box.png

line_box.png

3269 ms

bt-search.png

bt-search.png

3285 ms

spacer.gif

spacer.gif

3321 ms

14-05-13-14-12-57-s.jpg

14-05-13-14-12-57-s.jpg

3481 ms

line_ber.png

line_ber.png

3484 ms

14-05-13-14-13-49-s.png

14-05-13-14-13-49-s.png

3495 ms

12-09-16-17-02-19s.jpg

12-09-16-17-02-19s.jpg

3239 ms

t0031082.js

t0031082.js

1444 ms

ems.php

ems.php

3887 ms

THSarabun.ttf

THSarabun.ttf

2782 ms

THSarabun.woff

THSarabun.woff

3742 ms

15-05-16-22-20-29s.jpg

15-05-16-22-20-29s.jpg

3194 ms

button.gif

button.gif

2933 ms

about-footer3.png

about-footer3.png

2981 ms

bg-bersuay_01.png

bg-bersuay_01.png

2782 ms

bg-bersuay_02.png

bg-bersuay_02.png

2937 ms

bg-bersuay_03.png

bg-bersuay_03.png

2468 ms

bg-bersuay_04.png

bg-bersuay_04.png

2474 ms

bg-bersuay_06.png

bg-bersuay_06.png

2404 ms

bg-bersuay_10.png

bg-bersuay_10.png

2391 ms

bg-bersuay_11.png

bg-bersuay_11.png

2416 ms

bg-bersuay_12.png

bg-bersuay_12.png

2250 ms

saleout.gif

saleout.gif

2340 ms

06-07-13-21-54-08-s.jpg

06-07-13-21-54-08-s.jpg

2204 ms

spage.png

spage.png

2177 ms

bar.jpg

bar.jpg

2226 ms

text_footer01.png

text_footer01.png

4663 ms

shadow_line.png

shadow_line.png

2103 ms

qr_icon.png

qr_icon.png

3195 ms

list.gif

list.gif

3184 ms

bg_topm.png

bg_topm.png

1932 ms

side-pdbody.png

side-pdbody.png

1954 ms

side-pdbg.png

side-pdbg.png

2358 ms

bg_search.png

bg_search.png

2116 ms

bar-aboutus.png

bar-aboutus.png

2022 ms

about-bg.png

about-bg.png

2513 ms

bg-searchber.png

bg-searchber.png

2292 ms

bg-boxsearch.png

bg-boxsearch.png

2370 ms

bar-tops%20(1).png

bar-tops%20(1).png

2514 ms

about-bg3.png

about-bg3.png

2873 ms

bar-bersuay4.png

bar-bersuay4.png

2515 ms

bg-bersuay_07.png

bg-bersuay_07.png

2587 ms

bg-bersuay_007.png

bg-bersuay_007.png

2703 ms

bg-bersuay_09.png

bg-bersuay_09.png

2680 ms

bar-aboutus3.png

bar-aboutus3.png

2658 ms

linefooter.jpg

linefooter.jpg

2583 ms

bg-footer.jpg

bg-footer.jpg

3723 ms

Accessibility Review

noblesim.com accessibility score

41

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

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

High

Image elements do not have [alt] attributes

High

<input type="image"> elements do not have [alt] text

High

Form elements do not have associated labels

High

Links do not have a discernible name

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

Best Practices

noblesim.com best practices score

50

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

noblesim.com SEO score

67

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

Language and Encoding

  • Language Detected

    PT

  • Language Claimed

    N/A

  • Encoding

    WINDOWS-874

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Noblesim.com can be misinterpreted by Google and other search engines. Our service has detected that Portuguese 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 Noblesim.com main page’s claimed encoding is windows-874. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

noblesim.com

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