Tools & Wizards About Us
en.gemsnav.com screenshot

Report Summary

  • 78

    Performance

    Renders faster than
    85% of other websites

  • 60

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

en.gemsnav.com

GPS Repeater|GPS Splitter|GPS Antenna|GPS Over Fiber|Shield Box

Page Load Speed

5.6 sec in total

First Response

232 ms

Resources Loaded

3.5 sec

Page Rendered

1.9 sec

en.gemsnav.com screenshot

About Website

Welcome to en.gemsnav.com homepage info - get ready to check En Gemsnav best content right away, or after learning these important things about en.gemsnav.com

GEMS NAVIGATION was established in 2007, focusing on indoor positioning and timing technology. We are a Satellite navigation research and development centers and manufacturing plants.

Visit en.gemsnav.com

Key Findings

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

Performance Metrics

en.gemsnav.com performance score

78

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.9 s

87/100

10%

LCP (Largest Contentful Paint)

Value3.5 s

64/100

25%

SI (Speed Index)

Value3.5 s

88/100

10%

TBT (Total Blocking Time)

Value320 ms

76/100

30%

CLS (Cumulative Layout Shift)

Value0.14

79/100

15%

TTI (Time to Interactive)

Value2.3 s

99/100

10%

Network Requests Diagram

en.gemsnav.com

232 ms

en.gemsnav.com

526 ms

default.css

74 ms

component.css

136 ms

base.css

198 ms

Our browser made a total of 100 requests to load all elements on the main page. We found that 94% of them (94 requests) were addressed to the original En.gemsnav.com, 2% (2 requests) were made to Hm.baidu.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain En.gemsnav.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 264.5 kB (7%)

Content Size

3.8 MB

After Optimization

3.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-87%

Potential reduce by 42.8 kB

  • Original 49.0 kB
  • After minification 28.5 kB
  • After compression 6.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 20.4 kB, which is 42% 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 42.8 kB or 87% of the original size.

Image Optimization

-6%

Potential reduce by 219.3 kB

  • Original 3.7 MB
  • After minification 3.5 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. En Gemsnav images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 507 B

  • Original 55.2 kB
  • After minification 55.2 kB
  • After compression 54.7 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

-20%

Potential reduce by 1.9 kB

  • Original 9.1 kB
  • After minification 9.0 kB
  • After compression 7.3 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. En.gemsnav.com needs all CSS files to be minified and compressed as it can save up to 1.9 kB or 20% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (11%)

Requests Now

97

After Optimization

86

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

en.gemsnav.com

en.gemsnav.com

232 ms

en.gemsnav.com

en.gemsnav.com

526 ms

default.css

default.css

74 ms

component.css

component.css

136 ms

base.css

base.css

198 ms

swiper.min.js

swiper.min.js

285 ms

swiper.css

swiper.css

205 ms

index.css

index.css

211 ms

reset.css

reset.css

211 ms

public.css

public.css

218 ms

js

js

61 ms

jquery-1.8.3.min.js

jquery-1.8.3.min.js

332 ms

cbpHorizontalMenu.min.js

cbpHorizontalMenu.min.js

262 ms

hm.js

hm.js

1649 ms

company-logo.png

company-logo.png

168 ms

sousuo-logo.png

sousuo-logo.png

79 ms

banner4.jpg

banner4.jpg

800 ms

banner1.jpg

banner1.jpg

1581 ms

banner2.jpg

banner2.jpg

794 ms

233.jpg

233.jpg

294 ms

156.png

156.png

1088 ms

123.png

123.png

804 ms

T216.jpg

T216.jpg

588 ms

S208.jpg

S208.jpg

819 ms

10.jpg

10.jpg

1343 ms

574.jpg

574.jpg

1019 ms

IRGS208.jpg

IRGS208.jpg

1036 ms

iRGS216.jpg

iRGS216.jpg

1063 ms

12334587.jpg

12334587.jpg

1334 ms

6633.jpg

6633.jpg

1391 ms

123456.jpg

123456.jpg

1427 ms

logo.png

logo.png

1240 ms

header_logo.png

header_logo.png

1341 ms

b2f58ccbf3f7e2d9374fdb580c8b687a_222_222.png

b2f58ccbf3f7e2d9374fdb580c8b687a_222_222.png

1431 ms

ABUIABAEGAAgw5GO9gUosLYcMJMCOE0!160x160.png

ABUIABAEGAAgw5GO9gUosLYcMJMCOE0!160x160.png

1429 ms

9.png

9.png

1417 ms

8.png

8.png

1609 ms

7.png

7.png

1497 ms

6.png

6.png

1535 ms

5.png

5.png

1518 ms

%E5%8D%8E%E4%B8%BA.jpg

%E5%8D%8E%E4%B8%BA.jpg

1553 ms

VIVO.jpg

VIVO.jpg

1585 ms

%E8%8B%B9%E6%9E%9C.jpg

%E8%8B%B9%E6%9E%9C.jpg

1608 ms

%E5%AF%8C%E5%A3%AB%E5%BA%B7.jpg

%E5%AF%8C%E5%A3%AB%E5%BA%B7.jpg

1633 ms

quo.jpg

quo.jpg

1634 ms

FLEX.png

FLEX.png

1662 ms

mi.jpg

mi.jpg

1663 ms

honey.jpg

honey.jpg

1686 ms

byd.jpg

byd.jpg

1671 ms

%E6%AD%A6%E6%B1%89%E5%A4%A7%E5%AD%A6.jpg

%E6%AD%A6%E6%B1%89%E5%A4%A7%E5%AD%A6.jpg

1688 ms

%E8%81%94%E6%83%B3.jpg

%E8%81%94%E6%83%B3.jpg

1643 ms

%E5%8E%A6%E9%97%A8%E5%A4%A7%E5%AD%A6.jpg

%E5%8E%A6%E9%97%A8%E5%A4%A7%E5%AD%A6.jpg

1585 ms

ASUS.jpg

ASUS.jpg

1451 ms

HM.png

HM.png

1186 ms

%E7%B4%A2%E5%B0%BC.jpg

%E7%B4%A2%E5%B0%BC.jpg

984 ms

%E4%B8%8A%E6%B5%B7%E8%B4%9D%E5%B0%94.jpg

%E4%B8%8A%E6%B5%B7%E8%B4%9D%E5%B0%94.jpg

1049 ms

%E4%B8%AD%E5%85%B4.jpg

%E4%B8%AD%E5%85%B4.jpg

1043 ms

%E7%94%B5%E4%BF%A1.jpg

%E7%94%B5%E4%BF%A1.jpg

1031 ms

ZYKJ.jpg

ZYKJ.jpg

830 ms

TCL.jpg

TCL.jpg

834 ms

%E5%A4%A7%E5%94%90%E7%A7%BB%E5%8A%A8.jpg

%E5%A4%A7%E5%94%90%E7%A7%BB%E5%8A%A8.jpg

809 ms

HCN.jpg

HCN.jpg

784 ms

QZD.jpg

QZD.jpg

661 ms

RB.png

RB.png

633 ms

SIEMENS.png

SIEMENS.png

577 ms

SINCHUN.png

SINCHUN.png

622 ms

SKYPINE.png

SKYPINE.png

580 ms

BIRD.jpg

BIRD.jpg

559 ms

BJqw.jpg

BJqw.jpg

559 ms

GOSCAN.png

GOSCAN.png

566 ms

HP.jpg

HP.jpg

567 ms

MSD.jpg

MSD.jpg

509 ms

%E5%A4%A7%E8%BF%9E%E6%B5%B7%E4%BA%8B%E5%A4%A7%E5%AD%A6.jpg

%E5%A4%A7%E8%BF%9E%E6%B5%B7%E4%BA%8B%E5%A4%A7%E5%AD%A6.jpg

495 ms

APICAL.png

APICAL.png

489 ms

SIRF.png

SIRF.png

490 ms

JBTX.png

JBTX.png

493 ms

JWKJ.jpg

JWKJ.jpg

473 ms

OKTEK.png

OKTEK.png

468 ms

FORD.jpg

FORD.jpg

473 ms

hm.gif

hm.gif

353 ms

74-osa.png

74-osa.png

473 ms

73-qinghuadaxue.jpg

73-qinghuadaxue.jpg

489 ms

PT.png

PT.png

469 ms

sgm.jpg

sgm.jpg

479 ms

de.jpg

de.jpg

476 ms

ZT.jpg

ZT.jpg

502 ms

footer-dot.png

footer-dot.png

485 ms

facebook.png

facebook.png

481 ms

twitter.png

twitter.png

457 ms

LinkedIn.png

LinkedIn.png

461 ms

google.png

google.png

460 ms

ewm.png

ewm.png

525 ms

push.js

push.js

609 ms

phone.png

phone.png

419 ms

print.png

print.png

452 ms

xinxi.png

xinxi.png

417 ms

adress.png

adress.png

431 ms

skype.png

skype.png

439 ms

analytics.js

analytics.js

26 ms

collect

collect

39 ms

Accessibility Review

en.gemsnav.com accessibility score

60

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

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

en.gemsnav.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

en.gemsnav.com SEO score

89

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

High

Tap targets are not sized appropriately

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 En.gemsnav.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 En.gemsnav.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

en.gemsnav.com

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