85.4 sec in total
1.7 sec
83.3 sec
323 ms
Welcome to tryine.com homepage info - get ready to check Tryine best content right away, or after learning these important things about tryine.com
创研股份是一家技术驱动型全链路AI数智化服务商,业务范围主要包括:APP/小程序/系统等软件定制开发,腾讯/快手/京东/百度/巨量等数字媒介代理,广告投放代运营,短视频/直播/全案/新媒体运营等品牌推广;湖南数字技术/营销公司找创研,咨询电话0731-82233676
Visit tryine.comWe analyzed Tryine.com page load time and found that the first response time was 1.7 sec and then it took 83.6 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 53 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
tryine.com performance score
name
value
score
weighting
Value3.5 s
36/100
10%
Value3.9 s
53/100
25%
Value18.3 s
0/100
10%
Value340 ms
75/100
30%
Value0
100/100
15%
Value10.7 s
22/100
10%
1708 ms
8296 ms
8501 ms
12537 ms
3334 ms
Our browser made a total of 141 requests to load all elements on the main page. We found that 88% of them (124 requests) were addressed to the original Tryine.com, 6% (9 requests) were made to Bdimg.share.baidu.com and 3% (4 requests) were made to Lxbjs.baidu.com. The less responsive or slowest element that took the longest time to load (20.5 sec) belongs to the original domain Tryine.com.
Page size can be reduced by 233.0 kB (47%)
497.8 kB
264.7 kB
In fact, the total size of Tryine.com main page is 497.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 270.9 kB which makes up the majority of the site volume.
Potential reduce by 74.9 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 19.0 kB, which is 21% 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 74.9 kB or 82% of the original size.
Potential reduce by 74.1 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, Tryine needs image optimization as it can save up to 74.1 kB or 27% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 84.1 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 84.1 kB or 62% of the original size.
Number of requests can be reduced by 21 (24%)
86
65
The browser has sent 86 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tryine. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and as a result speed up the page load time.
tryine.com
1708 ms
www.tryine.com
8296 ms
jquery-1.8.2.min.js
8501 ms
jquery_tab.js
12537 ms
style.css
3334 ms
css.css
6026 ms
jquery-1.9.1.min.js
15515 ms
superslide.2.1.js
3424 ms
tab.js
3824 ms
slideshow.js
4876 ms
list_bur.js
4287 ms
nav_menu.js
4743 ms
lrtk.js
5232 ms
global_cn.index.js
5535 ms
w_xqe.png
581 ms
w_cy_ewm.jpg
7671 ms
t_wex.png
607 ms
w_eeee.png
1408 ms
t_web.png
468 ms
logo-tryine.png
1387 ms
hea_tell.png
879 ms
nav_pic1.jpg
3459 ms
nav_pic2.jpg
11541 ms
nav_pic3.jpg
9184 ms
wlxy.jpg
11047 ms
nav_pic4.jpg
10102 ms
c_maps.jpg
4595 ms
z_p01.png
8926 ms
z_p1.jpg
11664 ms
z_p2.jpg
19986 ms
z_hov2.png
10024 ms
z_p3.jpg
13029 ms
z_hov3.png
13491 ms
z_p4.png
12502 ms
z_hov4.png
19270 ms
f473e179-5d47-4c06-93e9-faf3642d47be.jpg
18163 ms
3ed64a1c-20d0-4687-a0f4-f3bf60dec856.jpg
17352 ms
f231f33a-7183-4669-9c4a-83f34cddf516.jpg
19981 ms
fd782079-163f-40ec-a0ce-cd7d291ffe56.jpg
19945 ms
4260c51d-a83b-430c-83f6-c8bdfadcd3ee.jpg
19980 ms
e8f3e5bf-03be-4daa-9482-f78b3a51933d.jpg
19980 ms
d134be02-33d1-4820-9461-c0f0a3757be6.jpg
19981 ms
23a40d5b-ca2d-4601-94f5-044498ca98e8.jpg
19981 ms
5c9fb540-6047-44b2-b4e4-ebacc83071fc.jpg
19981 ms
450706e2-cb89-47b7-9cbd-d91be4bd8b8c.jpg
19981 ms
31b1040f-4b56-4d16-853a-0aab36d6dc61.jpg
19981 ms
50f5d07c-75cb-449b-bde7-6e4e4f0cef2d.jpg
19982 ms
1f5ca15b-8d60-4062-8054-0b026ba92450.jpg
19982 ms
860dafdb-fc85-4d4e-a25a-8eccf2f25266.jpg
19982 ms
d9e99ffd-1240-44e2-ad08-4f07e2ab942c.jpg
19978 ms
share.js
695 ms
h.js
1325 ms
3ec8a87c-13cc-4dfa-8c35-b1f89322f2ce.jpg
19546 ms
8e10f8f9-989b-46bc-a291-f7eb4b95faf7.jpg
20427 ms
8a3a3571-1ed4-4e55-9dcb-0ff1bb7ff244.jpg
20399 ms
error.html
1733 ms
d2946789-2ee9-403b-b875-59ad976fcd73.jpg
20113 ms
f44c67c5-96df-4b48-8b22-4ec175b5c358.jpg
19605 ms
cc77cc0a-19f3-4555-9e97-7d1080909c8a.jpg
19598 ms
lxb.js
1945 ms
hm.gif
520 ms
rt.js
1273 ms
share_api.js
305 ms
share_view.js
646 ms
select_api.js
668 ms
select_view.js
660 ms
tangram.js
20075 ms
api_base.js
650 ms
view_base.js
328 ms
3642ab7f-7d32-4af9-9804-5e534667f2b6.jpg
19530 ms
log.gif
387 ms
_l.js
7551 ms
b094dd56-eb67-452b-9038-a26376a4d55c.jpg
19767 ms
logger.js
1467 ms
9435f271-f06c-4df6-9a0f-13acee2ce39b.jpg
19145 ms
12e872d3-5fb8-48be-b3b5-3fd59b05d2f0.jpg
20060 ms
7dd00b34-9163-425e-9563-04afca3c6b83.jpg
19804 ms
b7dec8c7-c48e-42aa-a0ce-4abb2a70dcff.png
19960 ms
30c2d642-7454-4c95-8c22-e42fc5332e78.png
14747 ms
ee6cc22a-df37-453e-b445-7178df48b779.png
19941 ms
log.gif
442 ms
90bb852a-e9dd-4b07-a102-c050a7740c8b.jpg
18071 ms
13ef3a52-5ca7-48f3-9d7e-1b6a60c74e88.png
20321 ms
d2bfcc87-dac8-408e-b46e-c39145c1a241.jpg
20480 ms
269ec93f-9bf2-4dd3-930f-e4e3d3c7f2a5.jpg
19955 ms
f80cb2cf-e65f-45d5-ad09-140e6dc5548a.png
17401 ms
b610650d-ad88-48c1-a80b-4936d887e626.jpg
19629 ms
1b4f3e86-eb9f-47d7-900c-d22cf5f6e79c.jpg
19819 ms
fc4b3510-0215-4c28-8827-72e3101aaabf.jpg
19716 ms
3e2dd1e1-3fdc-4cf6-aaea-d24464952719.png
13073 ms
bb2156c5-cf90-4ec0-9b1b-8430c9b57a68.png
16968 ms
66e6e547-8254-48f5-9fd4-9e47a4853b6b.jpg
19998 ms
803427e4-d02c-4437-99ab-f720d8c58cb4.jpg
19998 ms
kh_1.png
18744 ms
kh_2.png
19997 ms
kh_3.png
19347 ms
kh_4.png
19996 ms
kh_5.png
19771 ms
kh_6.png
19995 ms
kh_7.png
19996 ms
kh_8.png
19996 ms
kh_9.png
19996 ms
kh_10.png
19997 ms
kh_11.png
19991 ms
kh_12.png
19998 ms
a8b60273-7e35-43eb-880d-55e1a319fa3b.jpg
19998 ms
w_pdhgggg.png
19998 ms
50c17c3f-67be-49bc-bdd3-d5a7b0cf34db.jpg
19998 ms
176e5df0-1c4b-4909-af98-a4e0544ff5fb.jpg
19984 ms
9b53248e-4eba-4649-8b5f-de02db4bf2bf.jpg
20001 ms
1a60bc5d-5236-4558-9a45-a75baae6bbcc.jpg
19624 ms
5934b851-908c-47c4-bd8a-c67fe1dd491e.jpg
20137 ms
ef4b3ccf-8092-4431-ac20-637cb856de66.jpg
15667 ms
par1.png
17642 ms
par2.png
15173 ms
par3.png
14676 ms
par4.png
16081 ms
par5.png
14295 ms
ft_ewm.png
17630 ms
open_im.png
13616 ms
close_im.png
12864 ms
w_r_t.png
13101 ms
w_r_kj.png
13263 ms
w_r_b.png
9528 ms
f_more.png
9584 ms
hea_bg.png
8739 ms
nav-bgline.gif
8146 ms
8dc36407-14d9-4467-a8ca-4ccad953152a.jpg
19998 ms
875c8f2e-b61d-4075-98da-c41c3253797f.jpg
19648 ms
a4d1e324-0bca-47e5-a67c-f9deb04e1ba0.jpg
20221 ms
41412cd0-7bec-4293-98e5-100e3fb01d66.jpg
20001 ms
ban_w.png
9220 ms
pre_l.png
9785 ms
next_r.png
11869 ms
al_ico.png
12424 ms
al_ico2.png
13059 ms
mt_ico.png
13115 ms
new_ico.png
14613 ms
pre.png
15532 ms
next.png
15170 ms
ban_on.png
17095 ms
tryine.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a valid value for its [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
Image elements do not have [alt] attributes
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
tryine.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
tryine.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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
Document uses legible font sizes
ZH
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tryine.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 Tryine.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.
tryine.com
Open Graph description is not detected on the main page of Tryine. 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: