11.8 sec in total
1.3 sec
10.3 sec
221 ms
Visit 398.cn now to see the best up-to-date 398 content and also check out these interesting facts you probably never knew about 398.cn
398口腔网分享全国口腔医院、牙科医生、口腔案例、牙科资讯和优惠信息,提供牙齿矫正、种植牙、牙齿美白、牙周治疗项目在线咨询服务。
Visit 398.cnWe analyzed 398.cn page load time and found that the first response time was 1.3 sec and then it took 10.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
398.cn performance score
name
value
score
weighting
Value7.0 s
1/100
10%
Value7.5 s
4/100
25%
Value13.7 s
1/100
10%
Value50 ms
100/100
30%
Value0
100/100
15%
Value11.3 s
19/100
10%
1340 ms
207 ms
410 ms
609 ms
810 ms
Our browser made a total of 93 requests to load all elements on the main page. We found that 95% of them (88 requests) were addressed to the original 398.cn, 2% (2 requests) were made to Hm.baidu.com and 1% (1 request) were made to Duihua.398.cn. The less responsive or slowest element that took the longest time to load (4.4 sec) belongs to the original domain 398.cn.
Page size can be reduced by 173.8 kB (5%)
3.6 MB
3.4 MB
In fact, the total size of 398.cn main page is 3.6 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. 65% of websites need less resources to load. Images take 3.4 MB which makes up the majority of the site volume.
Potential reduce by 116.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. This page needs HTML code to be minified as it can gain 47.1 kB, which is 36% 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 116.6 kB or 89% of the original size.
Potential reduce by 56.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. 398 images are well optimized though.
Potential reduce by 91 B
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. This website has mostly compressed JavaScripts.
Potential reduce by 737 B
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. 398.cn has all CSS files already compressed.
Number of requests can be reduced by 8 (9%)
89
81
The browser has sent 89 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 398. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
www.398.cn
1340 ms
207 ms
caoch_list.css
410 ms
new_list.css
609 ms
jquery1.8.min.js
810 ms
iconfont.css
612 ms
index.js
610 ms
wydh.js
1330 ms
common.js
656 ms
hm.js
3827 ms
push.js
677 ms
m_weixin.png
207 ms
s_weixin.png
667 ms
logo1.png
205 ms
subnav_c_bg.png
204 ms
beijing.png
207 ms
20240509104737622.jpg
669 ms
20240509104756854.jpg
820 ms
20240415060104811.gif
616 ms
20240509104813660.jpg
618 ms
20240415060019636.gif
1036 ms
20240508035316413.jpg
823 ms
20240506043442518.jpg
826 ms
20240430115828206.jpg
892 ms
20240430113432778.jpg
1120 ms
20240428014809885.jpg
1026 ms
20210713065748808.jpg
1030 ms
20210910035329246.jpg
1247 ms
20210917044024660.jpg
1347 ms
20211111041420443.jpg
1238 ms
20220224045451942.jpg
1454 ms
20220304045051630.jpg
2324 ms
20220412022607850.jpg
2963 ms
20221001061559992.jpg
1661 ms
20221121102407107.jpg
2913 ms
20230109033347260.jpg
1576 ms
20200528040207888.jpg
2908 ms
20200528091728130.jpg
1804 ms
20200619022858679.jpg
2076 ms
20200628022520929.jpg
2028 ms
20200916024535929.jpg
2254 ms
20201020105118937.jpg
2284 ms
20210111030106288.jpg
2476 ms
20220106032942875.jpg
2488 ms
20220223020817158.jpg
2733 ms
20220418054551981.jpg
2698 ms
20200528021909190.jpg
2649 ms
iconfont.woff
2700 ms
20200528022645218.jpg
2721 ms
20200528025236602.jpg
2739 ms
20201116061137138.jpg
2900 ms
11.0.1.js
986 ms
20201228035629348.jpg
3117 ms
20210804112612727.jpg
2709 ms
20220316045127773.jpg
2482 ms
20220329032833289.jpg
3102 ms
20220402030949405.jpg
2817 ms
20220414031542481.jpg
2490 ms
20200528093744309.jpg
2545 ms
20200528094043671.jpg
2629 ms
20200601055613352.jpg
3950 ms
20200610035102660.jpg
4327 ms
20200703054646775.jpg
2692 ms
20200828091834908.jpg
2741 ms
20201109041958346.jpg
2697 ms
20220215022052716.jpg
4378 ms
20220812042725284.jpg
3459 ms
20221114062355148.jpg
2635 ms
20240509228208.jpg
3840 ms
20240509450528.jpg
2652 ms
20240509507637.jpg
2734 ms
20240509173357.jpg
2733 ms
20240227055225219.jpg
2910 ms
20240219051916332.jpg
2759 ms
20240205054621361.jpg
2899 ms
20240130060210801.jpg
2889 ms
20240119062828399.jpg
2744 ms
20240117055022406.jpg
2901 ms
20240117014831993.jpg
2743 ms
20240115041708777.jpg
2936 ms
20240115024108832.jpg
2844 ms
2728 ms
20240112051327634.jpg
2715 ms
20240509885963.jpg
2749 ms
20240509206133.jpg
2884 ms
20240509457375.jpg
3294 ms
20240509899652.jpg
2869 ms
index_ask_img.png
3342 ms
top-logo.png
2701 ms
ba.png
2579 ms
weixin.jpg
2705 ms
hm.gif
1827 ms
iconfont.ttf
402 ms
398.cn 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
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
Form elements do not have associated labels
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.
398.cn 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
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
398.cn 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
Tap targets are not sized appropriately
![]()
ZH
![]()
ZH
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 398.cn can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and it matches the claimed language. Our system also found out that 398.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.
398.cn
Open Graph description is not detected on the main page of 398. 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: