44.5 sec in total
525 ms
43.7 sec
286 ms
Welcome to ogl.cn homepage info - get ready to check Ogl best content right away, or after learning these important things about ogl.cn
Visit ogl.cnWe analyzed Ogl.cn page load time and found that the first response time was 525 ms and then it took 44 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there were 8 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
ogl.cn performance score
name
value
score
weighting
Value0
0/100
10%
Value0
0/100
25%
Value0
0/100
10%
Value0
0/100
30%
Value0.001
100/100
15%
Value0
0/100
10%
525 ms
1140 ms
1653 ms
1665 ms
734 ms
Our browser made a total of 72 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Ogl.cn, 18% (13 requests) were made to Pos.baidu.com and 13% (9 requests) were made to T11.baidu.com. The less responsive or slowest element that took the longest time to load (20.3 sec) relates to the external source T12.baidu.com.
Page size can be reduced by 341.3 kB (25%)
1.4 MB
1.0 MB
In fact, the total size of Ogl.cn main page is 1.4 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. 35% of websites need less resources to load. Images take 891.2 kB which makes up the majority of the site volume.
Potential reduce by 19.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. 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 19.9 kB or 84% of the original size.
Potential reduce by 5.0 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. Ogl images are well optimized though.
Potential reduce by 314.6 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 314.6 kB or 72% of the original size.
Potential reduce by 1.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. Ogl.cn needs all CSS files to be minified and compressed as it can save up to 1.8 kB or 68% of the original size.
Number of requests can be reduced by 18 (29%)
62
44
The browser has sent 62 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ogl. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and as a result speed up the page load time.
728.dragonparking.com
525 ms
oneclick.css
1140 ms
client2.js
1653 ms
track.js
1665 ms
dp.js
734 ms
ci.js
2860 ms
c.js
3691 ms
f.js
3375 ms
f.js
19982 ms
biz2.jpg
14851 ms
jcqm
743 ms
jcqm
771 ms
jcqm
1196 ms
uijs.php
945 ms
uijs.php
951 ms
jcqm
917 ms
uijs.php
3467 ms
jcqm
924 ms
jcqm
1426 ms
jcqm
1189 ms
jcqm
1604 ms
bg.png
582 ms
sync.htm
536 ms
jcqm
3139 ms
cpro.js
857 ms
jcqm
20250 ms
jcqm
1553 ms
icon_14px.png
502 ms
sync.htm
450 ms
jcqm
1220 ms
xuanfu_close.png
463 ms
adx.php
1013 ms
u=3434588058,4231195861&fm=76
3332 ms
u=1103901568,1319293858&fm=76
7913 ms
u=946365800,1338868273&fm=76
1786 ms
bg.png
546 ms
reduce_bd-logo1_oper.png
557 ms
u=1539509989,2071374545&fm=76
1791 ms
u=1333879337,2081791155&fm=76
5773 ms
u=965622740,1214875691&fm=76
15154 ms
u=1682973911,2208197335&fm=76
20327 ms
cm.gif
730 ms
adx.php
1662 ms
adx.php
575 ms
u=859788640,4152799556&fm=76
3429 ms
u=2026711654,2463192511&fm=76
19850 ms
u=3792442396,180395522&fm=76
6277 ms
u=927757086,1353737357&fm=76
8713 ms
u=948029639,1247973789&fm=76
19850 ms
u=1474580414,2089030550&fm=76
19850 ms
u=1683668816,1216567831&fm=76
3630 ms
u=1983566171,2271116995&fm=76
9198 ms
adx.php
522 ms
u=3492775180,3053852274&fm=76
3349 ms
u=1539087117,1142082672&fm=76
672 ms
u=3544409157,4019166995&fm=76
1685 ms
youku
561 ms
s.htm
1226 ms
sync.html
690 ms
sync_pos.htm
444 ms
adx.php
332 ms
closefeedback.min.js
265 ms
sync2r.htm
945 ms
reduce_promotion_oper.png
266 ms
bd_logo.png
509 ms
bg_rb.png
520 ms
u=3712825453,692518663&fm=76
20133 ms
u=1843764016,2308479081&fm=76
20134 ms
u=2121025579,2884219392&fm=76
11616 ms
u=1063916820,1256237774&fm=76
7693 ms
u=1618580013,1134049270&fm=76
11627 ms
u=3099914519,3438159371&fm=76
10609 ms
ogl.cn accessibility score
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
<frame> or <iframe> elements do not have a title
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 [lang] attribute
ogl.cn best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
ogl.cn SEO score
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ogl.cn can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Ogl.cn 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.
ogl.cn
Open Graph description is not detected on the main page of Ogl. 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: