Tools & Wizards About Us
focustar.net screenshot

Report Summary

  • 57

    Performance

    Renders faster than
    74% of other websites

  • 61

    Accessibility

    Visual factors better than
    that of 27% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

focustar.net

呼叫中心,广州呼叫中心系统,呼叫中心领航者_聚星源科技

Page Load Speed

43.9 sec in total

First Response

3.1 sec

Resources Loaded

40.4 sec

Page Rendered

353 ms

focustar.net screenshot

About Website

Visit focustar.net now to see the best up-to-date Focustar content and also check out these interesting facts you probably never knew about focustar.net

呼叫中心，呼叫中心系统，广州呼叫中心系统供应商聚星源科技(www.focustar.net)，从事呼叫中心系统搭建20年，致力于为企业提供项目咨询、管理和应用实施的一体化全媒体呼叫中心解决方案，拥有包括中国电信、中国联通、中国石油等超10000家成功案例，咨询热线：400-668-2833

Visit focustar.net

Key Findings

We analyzed Focustar.net page load time and found that the first response time was 3.1 sec and then it took 40.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there were 27 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

focustar.net performance score

57

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

34/100

10%

LCP (Largest Contentful Paint)

Value5.3 s

22/100

25%

SI (Speed Index)

Value5.0 s

63/100

10%

TBT (Total Blocking Time)

Value110 ms

97/100

30%

CLS (Cumulative Layout Shift)

Value0.386

27/100

15%

TTI (Time to Interactive)

Value3.7 s

91/100

10%

Network Requests Diagram

focustar.net

3147 ms

www.focustar.net

3520 ms

css_whir.css

7344 ms

jquery-1.4.2.min.js

4328 ms

main.js

6230 ms

Our browser made a total of 86 requests to load all elements on the main page. We found that 58% of them (50 requests) were addressed to the original Focustar.net, 19% (16 requests) were made to Qiao.baidu.com and 5% (4 requests) were made to Hm.baidu.com. The less responsive or slowest element that took the longest time to load (20.4 sec) belongs to the original domain Focustar.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 242.2 kB (55%)

Content Size

443.3 kB

After Optimization

201.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Focustar.net main page is 443.3 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 20% of websites need less resources to load. Javascripts take 198.4 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 24.4 kB

  • Original 33.7 kB
  • After minification 30.9 kB
  • After compression 9.3 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 24.4 kB or 72% of the original size.

Image Optimization

-21%

Potential reduce by 29.8 kB

  • Original 140.1 kB
  • After minification 110.3 kB

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, Focustar needs image optimization as it can save up to 29.8 kB or 21% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-65%

Potential reduce by 128.6 kB

  • Original 198.4 kB
  • After minification 197.2 kB
  • After compression 69.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 128.6 kB or 65% of the original size.

CSS Optimization

-84%

Potential reduce by 59.3 kB

  • Original 71.0 kB
  • After minification 52.2 kB
  • After compression 11.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. Focustar.net needs all CSS files to be minified and compressed as it can save up to 59.3 kB or 84% of the original size.

Requests Breakdown

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

Requests Now

56

After Optimization

28

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

focustar.net

focustar.net

3147 ms

www.focustar.net

www.focustar.net

3520 ms

css_whir.css

css_whir.css

7344 ms

jquery-1.4.2.min.js

jquery-1.4.2.min.js

4328 ms

main.js

main.js

6230 ms

o.php

o.php

10145 ms

stat.php

stat.php

2750 ms

jquery-latest.min.js

jquery-latest.min.js

13084 ms

unslider.min.js

unslider.min.js

1289 ms

bg_top.gif

bg_top.gif

5250 ms

top_tel.jpg

top_tel.jpg

7364 ms

logo.jpg

logo.jpg

4393 ms

banner1.gif

banner1.gif

20382 ms

banner2.gif

banner2.gif

20381 ms

banner3.gif

banner3.gif

20382 ms

banner4.jpg

banner4.jpg

20381 ms

bg_main.jpg

bg_main.jpg

5745 ms

bg_index_products.gif

bg_index_products.gif

8346 ms

20120711055641375.jpg

20120711055641375.jpg

11152 ms

20120723112123801.jpg

20120723112123801.jpg

10988 ms

20120711055711312.gif

20120711055711312.gif

12018 ms

20120711055726312.jpg

20120711055726312.jpg

14451 ms

20120723010227567.jpg

20120723010227567.jpg

20380 ms

20120723054110348.jpg

20120723054110348.jpg

20379 ms

20120723010252317.jpg

20120723010252317.jpg

20380 ms

20120723054054457.jpg

20120723054054457.jpg

20379 ms

title_news.gif

title_news.gif

20379 ms

1-160331142K1210.jpg

1-160331142K1210.jpg

20380 ms

dot01.gif

dot01.gif

20379 ms

title_tysq.gif

title_tysq.gif

20379 ms

pic_09.gif

pic_09.gif

20379 ms

bg_user.gif

bg_user.gif

20379 ms

title_user.gif

title_user.gif

20379 ms

chinamobile.gif

chinamobile.gif

20378 ms

meizu.gif

meizu.gif

20379 ms

isuzu.jpg

isuzu.jpg

20378 ms

aicai.png

aicai.png

20378 ms

water.jpg

water.jpg

20379 ms

shuzi.jpg

shuzi.jpg

20379 ms

tourism.gif

tourism.gif

20379 ms

hunan.gif

hunan.gif

20380 ms

cgb.jpg

cgb.jpg

20379 ms

dazu.gif

dazu.gif

20379 ms

2012072311163551.png

2012072311163551.png

20379 ms

stat.htm

stat.htm

303 ms

core.php

core.php

1504 ms

button_111.gif

button_111.gif

546 ms

9.gif

9.gif

1063 ms

pic1.gif

pic1.gif

817 ms

h.js

h.js

1154 ms

app.gif

app.gif

3822 ms

s.js

s.js

3143 ms

hm.gif

hm.gif

366 ms

h.js

h.js

1536 ms

21.gif

21.gif

744 ms

b.js

b.js

2441 ms

hm.gif

hm.gif

304 ms

2012072311164720.png

2012072311164720.png

16960 ms

20120723111703864.png

20120723111703864.png

18849 ms

20120723111714473.png

20120723111714473.png

20132 ms

20120723111725942.png

20120723111725942.png

15715 ms

bsl.js

bsl.js

2244 ms

20120723111736989.png

20120723111736989.png

14678 ms

20120723111747973.png

20120723111747973.png

17289 ms

Enter.php

Enter.php

835 ms

main_icon_invite_mess_api.js

main_icon_invite_mess_api.js

4756 ms

main.css

main.css

978 ms

fix.css

fix.css

5107 ms

version.js

version.js

5188 ms

20120723111802551.png

20120723111802551.png

11556 ms

m-webim-lite.css

m-webim-lite.css

1015 ms

m-webim-lite.js

m-webim-lite.js

1733 ms

Refresh.php

Refresh.php

406 ms

stat.gif

stat.gif

834 ms

12.png

12.png

6271 ms

14.png

14.png

6758 ms

icon.png

icon.png

738 ms

14_left.png

14_left.png

1190 ms

14_close.png

14_close.png

2858 ms

mess-text.png

mess-text.png

3252 ms

messbtn.png

messbtn.png

2190 ms

mess.gif

mess.gif

2730 ms

btn.png

btn.png

2810 ms

Refresh.php

Refresh.php

390 ms

nopic.gif

nopic.gif

4533 ms

Refresh.php

Refresh.php

410 ms

Accessibility Review

focustar.net accessibility score

61

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.

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

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

focustar.net best practices score

58

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

focustar.net SEO score

83

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

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

    GB2312

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Focustar.net 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 Focustar.net main page’s claimed encoding is gb2312. 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

focustar.net

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