Tools & Wizards About Us
neon-glo.com screenshot

Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

neon-glo.com

Event Party Supplies, Novelty, Theme Party - Wonderful

Page Load Speed

11.6 sec in total

First Response

379 ms

Resources Loaded

10.1 sec

Page Rendered

1.1 sec

neon-glo.com screenshot

About Website

Welcome to neon-glo.com homepage info - get ready to check Neon Glo best content right away, or after learning these important things about neon-glo.com

Wonderful enterprise Co., Ltd. has been carrying forward the spirit of craftsmanship. It has been working hard in this subdivision industry for many years.

Visit neon-glo.com

Key Findings

We analyzed Neon-glo.com page load time and found that the first response time was 379 ms and then it took 11.2 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

neon-glo.com performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

36/100

10%

LCP (Largest Contentful Paint)

Value7.6 s

3/100

25%

SI (Speed Index)

Value11.0 s

6/100

10%

TBT (Total Blocking Time)

Value1,260 ms

19/100

30%

CLS (Cumulative Layout Shift)

Value0.207

60/100

15%

TTI (Time to Interactive)

Value12.7 s

14/100

10%

Network Requests Diagram

neon-glo.com

379 ms

js

61 ms

style.css

393 ms

style2.css

593 ms

public.css

541 ms

Our browser made a total of 52 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Neon-glo.com, 65% (34 requests) were made to Cdn.globalso.com and 21% (11 requests) were made to Globalso.site. The less responsive or slowest element that took the longest time to load (9 sec) relates to the external source Cdn.globalso.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 153.6 kB (4%)

Content Size

4.2 MB

After Optimization

4.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Neon-glo.com main page is 4.2 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 3.6 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 44.3 kB

  • Original 52.7 kB
  • After minification 48.1 kB
  • After compression 8.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. 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 44.3 kB or 84% of the original size.

Image Optimization

-0%

Potential reduce by 9.9 kB

  • Original 3.6 MB
  • After minification 3.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. Neon Glo images are well optimized though.

JavaScript Optimization

-19%

Potential reduce by 78.4 kB

  • Original 419.4 kB
  • After minification 419.4 kB
  • After compression 341.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 78.4 kB or 19% of the original size.

CSS Optimization

-29%

Potential reduce by 21.0 kB

  • Original 71.7 kB
  • After minification 71.7 kB
  • After compression 50.7 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. Neon-glo.com needs all CSS files to be minified and compressed as it can save up to 21.0 kB or 29% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (37%)

Requests Now

46

After Optimization

29

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

neon-glo.com

neon-glo.com

379 ms

js

js

61 ms

style.css

style.css

393 ms

style2.css

style2.css

593 ms

public.css

public.css

541 ms

livechat.js

livechat.js

363 ms

form.js

form.js

364 ms

jquery.min.js

jquery.min.js

745 ms

common.js

common.js

546 ms

public.js

public.js

666 ms

271122-aigro-www.neon-glo.com.js

271122-aigro-www.neon-glo.com.js

710 ms

logo1.png

logo1.png

2681 ms

banner5.jpg

banner5.jpg

1578 ms

banner9.jpg

banner9.jpg

985 ms

banner231.jpg

banner231.jpg

954 ms

banner2.jpg

banner2.jpg

1030 ms

HTB1fX6EJ4SYBuNjSsphq6zGvVXaM.jpg

HTB1fX6EJ4SYBuNjSsphq6zGvVXaM.jpg

953 ms

He176554ad6ee4c96ac8e82a5af5b9f5dN.jpg

He176554ad6ee4c96ac8e82a5af5b9f5dN.jpg

1130 ms

HTB1ffFTG49YBuNjy0Ffq6xIsVXa6.jpg

HTB1ffFTG49YBuNjy0Ffq6xIsVXa6.jpg

1094 ms

HTB15fIqyBmWBuNkSndVq6AsApXaa.jpg

HTB15fIqyBmWBuNkSndVq6AsApXaa.jpg

2785 ms

HTB1p0GPXO6guuRjy1Xdq6yAwpXax.jpg

HTB1p0GPXO6guuRjy1Xdq6yAwpXax.jpg

1196 ms

HTB15exgGVOWBuNjy0Fiq6xFxVXa5.jpg

HTB15exgGVOWBuNjy0Fiq6xFxVXa5.jpg

1260 ms

HTB10PozBRmWBuNkSndVq6AsApXaE.jpg

HTB10PozBRmWBuNkSndVq6AsApXaE.jpg

1410 ms

HTB1oYfIkIIrBKNjSZK9q6ygoVXaY.jpg

HTB1oYfIkIIrBKNjSZK9q6ygoVXaY.jpg

1365 ms

js

js

73 ms

analytics.js

analytics.js

22 ms

collect

collect

33 ms

title_pic.png

title_pic.png

1159 ms

2024228_inquiry_livechat_neon-glocom

2024228_inquiry_livechat_neon-glocom

448 ms

search_btn.png

search_btn.png

1145 ms

all-m.gif

all-m.gif

1293 ms

jiantou_03.png

jiantou_03.png

2005 ms

jiantou_01.png

jiantou_01.png

1239 ms

about_bg.png

about_bg.png

4118 ms

icons01.png

icons01.png

1990 ms

whatsapppic.png

whatsapppic.png

1744 ms

close.png

close.png

2937 ms

show_btn.png

show_btn.png

2231 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

2178 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

2309 ms

SourceHanSansSC-BOLD.OTF

SourceHanSansSC-BOLD.OTF

9028 ms

SourceHanSansSC-Regular.otf

SourceHanSansSC-Regular.otf

8719 ms

2024228_inquiry_form_neon-glocom

2024228_inquiry_form_neon-glocom

459 ms

search_btn_close.png

search_btn_close.png

2453 ms

statistic.php

statistic.php

2087 ms

from_livechat.css

from_livechat.css

7 ms

jquery.min.js

jquery.min.js

14 ms

layer.js

layer.js

29 ms

group_oper.js

group_oper.js

33 ms

validform.min.js

validform.min.js

33 ms

jquery.cookie.js

jquery.cookie.js

34 ms

layer.css

layer.css

13 ms

Accessibility Review

neon-glo.com accessibility score

86

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

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

neon-glo.com best practices score

75

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

SEO Factors

neon-glo.com SEO score

85

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

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

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 Neon-glo.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 Neon-glo.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

neon-glo.com

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