Tools & Wizards About Us
sou.com screenshot

Report Summary

  • 48

    Performance

    Renders faster than
    67% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 80

    SEO

    Google-friendlier than
    42% of websites

sou.com

360搜索，SO靠谱

Page Load Speed

8.6 sec in total

First Response

858 ms

Resources Loaded

7.5 sec

Page Rendered

205 ms

sou.com screenshot

About Website

Welcome to sou.com homepage info - get ready to check Sou best content for China right away, or after learning these important things about sou.com

360搜索是安全、精准、可信赖的新一代搜索引擎，依托于360母品牌的安全优势，全面拦截各类钓鱼欺诈等恶意网站，提供更放心的搜索服务。 360搜索 so靠谱。

Visit sou.com

Key Findings

We analyzed Sou.com page load time and found that the first response time was 858 ms and then it took 7.7 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

sou.com performance score

48

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.4 s

7/100

10%

LCP (Largest Contentful Paint)

Value5.6 s

17/100

25%

SI (Speed Index)

Value9.6 s

11/100

10%

TBT (Total Blocking Time)

Value380 ms

70/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value6.8 s

55/100

10%

Network Requests Diagram

sou.com

858 ms

sou.com

2079 ms

del.png

948 ms

183.js

916 ms

main.js

1001 ms

Our browser made a total of 84 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Sou.com, 50% (42 requests) were made to So.360tres.com and 14% (12 requests) were made to So1.360tres.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Sou.com.

Page Optimization Overview & Recommendations

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

Content Size

445.3 kB

After Optimization

198.3 kB

  • HTML
  • Images

In fact, the total size of Sou.com main page is 445.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. 35% of websites need less resources to load. HTML takes 296.5 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 232.2 kB

  • Original 296.5 kB
  • After minification 287.2 kB
  • After compression 64.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 232.2 kB or 78% of the original size.

Image Optimization

-10%

Potential reduce by 14.8 kB

  • Original 148.8 kB
  • After minification 133.9 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. Sou images are well optimized though.

Requests Breakdown

Number of requests can be reduced by 21 (26%)

Requests Now

80

After Optimization

59

  • AJAX
  • Images
  • JavaScript

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

Network Requests Diagram

sou.com

sou.com

858 ms

sou.com

sou.com

2079 ms

del.png

del.png

948 ms

183.js

183.js

916 ms

main.js

main.js

1001 ms

sad.js

sad.js

747 ms

foot.js

foot.js

1086 ms

placeholder_rec

placeholder_rec

1527 ms

home.gif

home.gif

1114 ms

cloud_config

cloud_config

1537 ms

getIds

getIds

1100 ms

s

s

1317 ms

s

s

1522 ms

cors

cors

1246 ms

query_rec

query_rec

1503 ms

Dataapi

Dataapi

1703 ms

require.min.js

require.min.js

68 ms

loader.js

loader.js

70 ms

t01a214fd02e70ced77.gif

t01a214fd02e70ced77.gif

69 ms

mlist

mlist

1245 ms

t0105b7f87fb2f3ddbd.png

t0105b7f87fb2f3ddbd.png

907 ms

t01b71887dfbffe0c36.png

t01b71887dfbffe0c36.png

102 ms

t018739ebfc70b0c1ce.png

t018739ebfc70b0c1ce.png

170 ms

t01f12091d80d748c4c.png

t01f12091d80d748c4c.png

200 ms

t01443d646aceb407f7.png

t01443d646aceb407f7.png

203 ms

click.gif

click.gif

856 ms

click.gif

click.gif

852 ms

t0157ed22793d789bea.png

t0157ed22793d789bea.png

897 ms

t015fcceea0c24e8155.png

t015fcceea0c24e8155.png

896 ms

t01f8fff0016e4abb07.png

t01f8fff0016e4abb07.png

200 ms

s

s

349 ms

t01dd682837846b59bb.webp

t01dd682837846b59bb.webp

110 ms

t0129041a30aba4db0b.png

t0129041a30aba4db0b.png

102 ms

click.gif

click.gif

232 ms

t0135287d5ab7ec8a7d.png

t0135287d5ab7ec8a7d.png

81 ms

click.gif

click.gif

220 ms

t0144453c17d144a7e8.webp

t0144453c17d144a7e8.webp

75 ms

t01ef2978df7c748eee.webp

t01ef2978df7c748eee.webp

76 ms

t019af20b92cc31f674.webp

t019af20b92cc31f674.webp

141 ms

t0123e2a2b8b90a0bfe.webp

t0123e2a2b8b90a0bfe.webp

142 ms

t0108f5eda6a9d185ec.webp

t0108f5eda6a9d185ec.webp

144 ms

t0177841a5d9aa929aa.webp

t0177841a5d9aa929aa.webp

207 ms

t0182632ddaac8b68ac.webp

t0182632ddaac8b68ac.webp

208 ms

t01c1e6a60c5e26698d.webp

t01c1e6a60c5e26698d.webp

212 ms

t010dc9ef680fcc95f0.webp

t010dc9ef680fcc95f0.webp

211 ms

t01424868b36cb3b584.webp

t01424868b36cb3b584.webp

273 ms

t014576d37ea972cc15.webp

t014576d37ea972cc15.webp

273 ms

t01f8ccdf76691a1cca.webp

t01f8ccdf76691a1cca.webp

277 ms

t013263486e96a83259.webp

t013263486e96a83259.webp

276 ms

t01e6756952cc2e059c.webp

t01e6756952cc2e059c.webp

278 ms

t01e716c2a8ae3a48de.webp

t01e716c2a8ae3a48de.webp

279 ms

t014774067d1350f4fc.webp

t014774067d1350f4fc.webp

339 ms

t015e9ae4d6d7c4db6e.webp

t015e9ae4d6d7c4db6e.webp

339 ms

t01f34364edeb2d17bc.webp

t01f34364edeb2d17bc.webp

341 ms

t0196008749156e4679.webp

t0196008749156e4679.webp

342 ms

t01acc8fa1e1d399196.webp

t01acc8fa1e1d399196.webp

344 ms

t0161ca13b6b1f53e92.webp

t0161ca13b6b1f53e92.webp

346 ms

t013591f8e8f25d6687.webp

t013591f8e8f25d6687.webp

406 ms

t016f8aac372d0b73cc.webp

t016f8aac372d0b73cc.webp

404 ms

t0143823aa878ac63ef.webp

t0143823aa878ac63ef.webp

408 ms

t014eec65d2150af494.webp

t014eec65d2150af494.webp

407 ms

t013fa4ea7b59011abc.webp

t013fa4ea7b59011abc.webp

415 ms

t014987905dd0e7dd06.webp

t014987905dd0e7dd06.webp

415 ms

t017e7e3d8f9a9b9abf.webp

t017e7e3d8f9a9b9abf.webp

471 ms

t0152f6f6766ed30ba3.webp

t0152f6f6766ed30ba3.webp

472 ms

t0121f58c3cf98479c1.webp

t0121f58c3cf98479c1.webp

473 ms

t01a3a3b3336fa5ce1d.png

t01a3a3b3336fa5ce1d.png

498 ms

t0167a4fdc3cb0263db.jpg

t0167a4fdc3cb0263db.jpg

1951 ms

t0169c93275f2f3cce4.png

t0169c93275f2f3cce4.png

67 ms

t0151692c7e75b432d3.png

t0151692c7e75b432d3.png

69 ms

t01c62f089fb255c48a.png

t01c62f089fb255c48a.png

68 ms

t01b2cc4b9f98de1251.ico

t01b2cc4b9f98de1251.ico

423 ms

t010fb5a321c9704e03.ico

t010fb5a321c9704e03.ico

427 ms

t0194c2350d3de0883d.ico

t0194c2350d3de0883d.ico

430 ms

t013ec025a409b8941b.ico

t013ec025a409b8941b.ico

486 ms

t01ac78fa7e2e7a7d0f.ico

t01ac78fa7e2e7a7d0f.ico

487 ms

t01a85f3b5f5bc0b67d.jpg

t01a85f3b5f5bc0b67d.jpg

1056 ms

t016ff617412355a892.jpg

t016ff617412355a892.jpg

991 ms

t01b00fe3809dcd3da0.ico

t01b00fe3809dcd3da0.ico

469 ms

t016bf7902f888dc34d.ico

t016bf7902f888dc34d.ico

469 ms

t013e77cbd9684c6bfb.ico

t013e77cbd9684c6bfb.ico

471 ms

s

s

242 ms

click.gif

click.gif

221 ms

click.gif

click.gif

213 ms

Accessibility Review

sou.com accessibility score

74

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

[aria-hidden="true"] elements contain focusable descendents

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

sou.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

sou.com SEO score

80

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

High

Tap targets are not sized appropriately

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 Sou.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 Sou.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

sou.com

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