Report Summary

  • 12

    Performance

    Renders faster than
    25% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 50% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

onloon.net

盈店通Onloon-10年专注外贸推广获客品牌服务丨外贸企业客户管理系统丨Facebook推广丨Google推广

Page Load Speed

11.6 sec in total

First Response

676 ms

Resources Loaded

9.6 sec

Page Rendered

1.3 sec

onloon.net screenshot

About Website

Welcome to onloon.net homepage info - get ready to check Onloon best content for United States right away, or after learning these important things about onloon.net

盈店通(www.onloon.net),是龙席网络旗下一款专注外贸企业营销客户管理SaaS系统,旨在为外贸出口型企业和工厂提供外贸企业独立站建设、外贸培训、外贸推广、外贸获客及外贸CRM等一站式服务。我们为盈店通用户完成了与Facebook、Pinterest、Twitter等国外社交平台对接,轻松触达30亿国外外贸客户,帮助外贸企业通过盈店通“多、快、好、省”做生意,推动中国外贸进入新时代。

Visit onloon.net

Key Findings

We analyzed Onloon.net page load time and found that the first response time was 676 ms and then it took 10.9 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

onloon.net performance score

12

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.3 s

1/100

10%

LCP (Largest Contentful Paint)

Value13.4 s

0/100

25%

SI (Speed Index)

Value24.4 s

0/100

10%

TBT (Total Blocking Time)

Value6,440 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.156

74/100

15%

TTI (Time to Interactive)

Value16.7 s

5/100

10%

Network Requests Diagram

www.onloon.net

676 ms

www.onloon.net

1116 ms

css

79 ms

bootstrap.min.css

741 ms

nice-select.css

615 ms

Our browser made a total of 85 requests to load all elements on the main page. We found that 88% of them (75 requests) were addressed to the original Onloon.net, 8% (7 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Hm.baidu.com. The less responsive or slowest element that took the longest time to load (4.9 sec) belongs to the original domain Onloon.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 314.5 kB (10%)

Content Size

3.1 MB

After Optimization

2.8 MB

In fact, the total size of Onloon.net main page is 3.1 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 2.9 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 50.5 kB

  • Original 60.0 kB
  • After minification 45.9 kB
  • After compression 9.6 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 14.1 kB, which is 24% 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 50.5 kB or 84% of the original size.

Image Optimization

-7%

Potential reduce by 196.7 kB

  • Original 2.9 MB
  • After minification 2.7 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. Onloon images are well optimized though.

JavaScript Optimization

-36%

Potential reduce by 45.6 kB

  • Original 127.5 kB
  • After minification 123.5 kB
  • After compression 81.9 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 45.6 kB or 36% of the original size.

CSS Optimization

-24%

Potential reduce by 21.7 kB

  • Original 90.5 kB
  • After minification 90.5 kB
  • After compression 68.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. Onloon.net needs all CSS files to be minified and compressed as it can save up to 21.7 kB or 24% of the original size.

Requests Breakdown

Number of requests can be reduced by 33 (43%)

Requests Now

76

After Optimization

43

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

Accessibility Review

onloon.net accessibility score

80

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[role]s are not contained by their required parent element

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

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

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

onloon.net 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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

onloon.net SEO score

91

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    ZH

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Onloon.net can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and it matches the claimed language. Our system also found out that Onloon.net 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

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