Tools & Wizards About Us
361pt.com screenshot

Report Summary

  • 71

    Performance

    Renders faster than
    82% 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

  • 99

    SEO

    Google-friendlier than
    93% of websites

361pt.com

91操视频_91康先生97年张倩琳在线_91免费精品视频_91视频站

Page Load Speed

20 sec in total

First Response

599 ms

Resources Loaded

18.7 sec

Page Rendered

706 ms

361pt.com screenshot

About Website

Visit 361pt.com now to see the best up-to-date 361 Pt content and also check out these interesting facts you probably never knew about 361pt.com

91视频 91视频二维码第一时间观看最新91在线视频,91+视频,视频一区,播放流畅,无卡顿.在线视频只适合18岁或以上人士观看,一款功能十分强大的视频播放软件福利短视频app 类型:影视视频 平台

Visit 361pt.com

Key Findings

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

Performance Metrics

361pt.com performance score

71

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

85/100

10%

LCP (Largest Contentful Paint)

Value4.1 s

47/100

25%

SI (Speed Index)

Value3.3 s

90/100

10%

TBT (Total Blocking Time)

Value110 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0.533

14/100

15%

TTI (Time to Interactive)

Value2.2 s

99/100

10%

Network Requests Diagram

361pt.com

599 ms

www.361pt.com

721 ms

css.css

153 ms

main.css

521 ms

zuowen.js

161 ms

Our browser made a total of 76 requests to load all elements on the main page. We found that 25% of them (19 requests) were addressed to the original 361pt.com, 54% (41 requests) were made to W88120.com and 4% (3 requests) were made to Hm.baidu.com. The less responsive or slowest element that took the longest time to load (15.9 sec) relates to the external source Tajs.qq.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 141.9 kB (35%)

Content Size

408.8 kB

After Optimization

266.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of 361pt.com main page is 408.8 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. 25% of websites need less resources to load. Images take 341.3 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 26.8 kB

  • Original 33.3 kB
  • After minification 33.0 kB
  • After compression 6.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. 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 26.8 kB or 80% of the original size.

Image Optimization

-26%

Potential reduce by 88.6 kB

  • Original 341.3 kB
  • After minification 252.7 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, 361 Pt needs image optimization as it can save up to 88.6 kB or 26% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-58%

Potential reduce by 3.8 kB

  • Original 6.6 kB
  • After minification 5.9 kB
  • After compression 2.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 3.8 kB or 58% of the original size.

CSS Optimization

-83%

Potential reduce by 22.8 kB

  • Original 27.6 kB
  • After minification 23.1 kB
  • After compression 4.8 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. 361pt.com needs all CSS files to be minified and compressed as it can save up to 22.8 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 9 (15%)

Requests Now

61

After Optimization

52

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

361pt.com

361pt.com

599 ms

www.361pt.com

www.361pt.com

721 ms

css.css

css.css

153 ms

main.css

main.css

521 ms

zuowen.js

zuowen.js

161 ms

jyb.js

jyb.js

162 ms

ad_js.php

ad_js.php

165 ms

ad_js.php

ad_js.php

162 ms

footer1.js

footer1.js

161 ms

51la.js

51la.js

172 ms

www.w88120.com

www.w88120.com

1633 ms

beij.gif

beij.gif

83 ms

logo.png

logo.png

442 ms

beijn.gif

beijn.gif

365 ms

tubiaon.gif

tubiaon.gif

526 ms

tubiao.gif

tubiao.gif

326 ms

zhongkao_bg.gif

zhongkao_bg.gif

85 ms

gaokao_bg.gif

gaokao_bg.gif

130 ms

nz_flbg.gif

nz_flbg.gif

164 ms

nav_flinkbg.gif

nav_flinkbg.gif

210 ms

18635562.js

18635562.js

761 ms

stats

stats

15940 ms

index.css

index.css

219 ms

time.js

time.js

429 ms

time1.js

time1.js

465 ms

1687 ms

tj.js

tj.js

476 ms

hm.js

hm.js

1575 ms

w88home.gif

w88home.gif

1328 ms

guoqi1.png

guoqi1.png

417 ms

guoqi2.png

guoqi2.png

643 ms

guoqi3.png

guoqi3.png

428 ms

guoqi4.png

guoqi4.png

441 ms

guoqi.png

guoqi.png

662 ms

960x60-CN.gif

960x60-CN.gif

2337 ms

content_bg.png

content_bg.png

1276 ms

text_spc_sp.jpg

text_spc_sp.jpg

873 ms

weixin.png

weixin.png

856 ms

sina.png

sina.png

879 ms

tencent.png

tencent.png

1072 ms

bbin.png

bbin.png

1093 ms

ag.png

ag.png

1094 ms

mg.png

mg.png

1287 ms

bottom1.png

bottom1.png

1311 ms

bottom2.png

bottom2.png

1309 ms

bottom3.png

bottom3.png

1481 ms

bottom4.png

bottom4.png

1503 ms

bottom5.png

bottom5.png

1525 ms

bottom6.png

bottom6.png

1528 ms

bottom7.png

bottom7.png

1534 ms

bottom8.png

bottom8.png

1692 ms

unionpay.png

unionpay.png

1932 ms

mastercard.png

mastercard.png

1740 ms

visa.png

visa.png

1746 ms

google.png

google.png

1752 ms

firefox.png

firefox.png

1902 ms

ie.png

ie.png

1953 ms

120x500-CN.gif

120x500-CN.gif

2849 ms

0.7866698808502406

0.7866698808502406

4974 ms

0.11500200652517378

0.11500200652517378

514 ms

0.8041819965001196

0.8041819965001196

507 ms

0.7081975070759654

0.7081975070759654

467 ms

0.9768946482799947

0.9768946482799947

3773 ms

0.28963934374041855

0.28963934374041855

2879 ms

0.3480402771383524

0.3480402771383524

1813 ms

0.9428721256554127

0.9428721256554127

2386 ms

0.6156298951245844

0.6156298951245844

4974 ms

xz.png

xz.png

1754 ms

xzc.png

xzc.png

1899 ms

xzb.png

xzb.png

1928 ms

xze.png

xze.png

1949 ms

sxan.jpg

sxan.jpg

1956 ms

text_sp.jpg

text_sp.jpg

2087 ms

18735340.js

18735340.js

717 ms

hm.gif

hm.gif

428 ms

hm.gif

hm.gif

424 ms

Accessibility Review

361pt.com 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.

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

Form elements do not have associated labels

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

361pt.com 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

SEO Factors

361pt.com SEO score

99

Search Engine Optimization Advices

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

    GB2312

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 361pt.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 361pt.com 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

361pt.com

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