Tools & Wizards About Us
fullgood.com screenshot

Report Summary

  • 26

    Performance

    Renders faster than
    45% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

fullgood.com

上順電子股份有限公司

Page Load Speed

9.8 sec in total

First Response

611 ms

Resources Loaded

8.8 sec

Page Rendered

353 ms

fullgood.com screenshot

About Website

Welcome to fullgood.com homepage info - get ready to check Fullgood best content right away, or after learning these important things about fullgood.com

上順電子股份有限公司

Visit fullgood.com

Key Findings

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

Performance Metrics

fullgood.com performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

12/100

10%

LCP (Largest Contentful Paint)

Value27.1 s

0/100

25%

SI (Speed Index)

Value15.7 s

0/100

10%

TBT (Total Blocking Time)

Value290 ms

80/100

30%

CLS (Cumulative Layout Shift)

Value0.906

3/100

15%

TTI (Time to Interactive)

Value14.6 s

8/100

10%

Network Requests Diagram

fullgood.com

611 ms

fullgood.com

2359 ms

font-awesome.min.css

611 ms

jquery-1.9.1.min.js

1284 ms

js

57 ms

Our browser made a total of 86 requests to load all elements on the main page. We found that 93% of them (80 requests) were addressed to the original Fullgood.com, 2% (2 requests) were made to Googletagmanager.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3.8 sec) belongs to the original domain Fullgood.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 10.5 MB (54%)

Content Size

19.6 MB

After Optimization

9.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-73%

Potential reduce by 158.5 kB

  • Original 215.8 kB
  • After minification 215.1 kB
  • After compression 57.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 158.5 kB or 73% of the original size.

Image Optimization

-54%

Potential reduce by 10.3 MB

  • Original 19.1 MB
  • After minification 8.8 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. Obviously, Fullgood needs image optimization as it can save up to 10.3 MB or 54% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-25%

Potential reduce by 53.8 kB

  • Original 215.6 kB
  • After minification 215.4 kB
  • After compression 161.8 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 53.8 kB or 25% of the original size.

CSS Optimization

-38%

Potential reduce by 26.8 kB

  • Original 69.9 kB
  • After minification 69.8 kB
  • After compression 43.1 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. Fullgood.com needs all CSS files to be minified and compressed as it can save up to 26.8 kB or 38% of the original size.

Requests Breakdown

Number of requests can be reduced by 36 (50%)

Requests Now

72

After Optimization

36

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fullgood.com

fullgood.com

611 ms

fullgood.com

fullgood.com

2359 ms

font-awesome.min.css

font-awesome.min.css

611 ms

jquery-1.9.1.min.js

jquery-1.9.1.min.js

1284 ms

js

js

57 ms

jquery.colorbox.user.js

jquery.colorbox.user.js

1065 ms

colorbox.css

colorbox.css

805 ms

def_system.js

def_system.js

825 ms

aos.css

aos.css

833 ms

slidebars.css

slidebars.css

810 ms

slidebars.min.js

slidebars.min.js

1003 ms

def.js

def.js

897 ms

color.css

color.css

910 ms

def_index_size_system.css

def_index_size_system.css

839 ms

tabs-no-images.css

tabs-no-images.css

1010 ms

aos.js

aos.js

1160 ms

rwd.css

rwd.css

1165 ms

rwd_system.css

rwd_system.css

1167 ms

rwd-basic.js

rwd-basic.js

1169 ms

floatlink.js

floatlink.js

1210 ms

FloatLink_1.css

FloatLink_1.css

1288 ms

hamburgers.css

hamburgers.css

1317 ms

nav-layout_merge_system.css

nav-layout_merge_system.css

1314 ms

def_MenuFadeOff_system.js

def_MenuFadeOff_system.js

1301 ms

def_ShowPhotoAnimator2.css

def_ShowPhotoAnimator2.css

1356 ms

jquery.mmenu.all.merge_system.css

jquery.mmenu.all.merge_system.css

1434 ms

jquery.mmenu.min.all.js

jquery.mmenu.min.all.js

1539 ms

menu_1_system.css

menu_1_system.css

1495 ms

index1.css

index1.css

1527 ms

def_hover_system.css

def_hover_system.css

1552 ms

smartphoto.min.js

smartphoto.min.js

1820 ms

smartphoto.min.css

smartphoto.min.css

1635 ms

animate.min.css

animate.min.css

1713 ms

slick.css

slick.css

1733 ms

slick-theme.css

slick-theme.css

1739 ms

slick.js

slick.js

1805 ms

smartphoto.js

smartphoto.js

2102 ms

owl.carousel.css

owl.carousel.css

1734 ms

owl.theme.default.min.css

owl.theme.default.min.css

1757 ms

owl.carousel.min.js

owl.carousel.min.js

1597 ms

bg.gif

bg.gif

885 ms

blank.gif

blank.gif

900 ms

logo4.png

logo4.png

1076 ms

16b.jpg

16b.jpg

2231 ms

18b.jpg

18b.jpg

2111 ms

19b.jpg

19b.jpg

2087 ms

17b.jpg

17b.jpg

2120 ms

20b.jpg

20b.jpg

2181 ms

21b.jpg

21b.jpg

2291 ms

609_1b.png

609_1b.png

2309 ms

%E4%B8%8A%E9%A0%86%E9%9B%BB%E5%AD%90%E4%BC%81%E6%A5%AD-06.png

%E4%B8%8A%E9%A0%86%E9%9B%BB%E5%AD%90%E4%BC%81%E6%A5%AD-06.png

2286 ms

616_3b.png

616_3b.png

2295 ms

611_1b.jpg

611_1b.jpg

2413 ms

611_2b.jpg

611_2b.jpg

2409 ms

js

js

53 ms

analytics.js

analytics.js

23 ms

611_3b.jpg

611_3b.jpg

2451 ms

611_4b.jpg

611_4b.jpg

2453 ms

collect

collect

33 ms

collect

collect

33 ms

%E4%B8%8A%E9%A0%86%E9%9B%BB%E5%AD%90%E4%BC%81%E6%A5%AD-11.png

%E4%B8%8A%E9%A0%86%E9%9B%BB%E5%AD%90%E4%BC%81%E6%A5%AD-11.png

2380 ms

ga-audiences

ga-audiences

36 ms

618_2b.png

618_2b.png

2407 ms

%E4%B8%8A%E9%A0%86%E9%9B%BB%E5%AD%90%E4%BC%81%E6%A5%AD_LOGO%20%E8%A4%87%E6%9C%AC.png

%E4%B8%8A%E9%A0%86%E9%9B%BB%E5%AD%90%E4%BC%81%E6%A5%AD_LOGO%20%E8%A4%87%E6%9C%AC.png

2495 ms

%E4%BB%95%E5%B7%9D%E7%B6%B2%E7%AB%99-18.png

%E4%BB%95%E5%B7%9D%E7%B6%B2%E7%AB%99-18.png

2443 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

2487 ms

divmain.jpg

divmain.jpg

2426 ms

divtop.jpg

divtop.jpg

2382 ms

divbottom.jpg

divbottom.jpg

2380 ms

logo.png

logo.png

2426 ms

top_menu_bg.gif

top_menu_bg.gif

2448 ms

loading.gif

loading.gif

2419 ms

b05.png

b05.png

2359 ms

a21.png

a21.png

2344 ms

bg2.gif

bg2.gif

2366 ms

jump1.png

jump1.png

2373 ms

bg_default.jpg

bg_default.jpg

2375 ms

609.jpg

609.jpg

2241 ms

616.jpg

616.jpg

2189 ms

612.jpg

612.jpg

2177 ms

617.jpg

617.jpg

3843 ms

615.jpg

615.jpg

2454 ms

divblockbottom.jpg

divblockbottom.jpg

2217 ms

ending_bg.gif

ending_bg.gif

2258 ms

overlay.png

overlay.png

1347 ms

ui.totop.png

ui.totop.png

1384 ms

Accessibility Review

fullgood.com accessibility score

74

Accessibility Issues

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

fullgood.com 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

Page has valid source maps

SEO Factors

fullgood.com 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

    ZH

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fullgood.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese 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 Fullgood.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

fullgood.com

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