14.2 sec in total
1.8 sec
12 sec
309 ms
Click here to check amazing Nav 123 content. Otherwise, check out these important facts you probably never knew about nav123.com
nav123世界网址导航是全球首屈一指的全世界网站分类导航网站,上网最快最安全便捷,网址导航自定义,全球众多的导航分类清晰为用户提供最快最好的上网方案也是全球国际网站汇聚地!
Visit nav123.comWe analyzed Nav123.com page load time and found that the first response time was 1.8 sec and then it took 12.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
nav123.com performance score
name
value
score
weighting
Value4.5 s
15/100
10%
Value6.5 s
9/100
25%
Value9.5 s
11/100
10%
Value1,190 ms
21/100
30%
Value0.032
100/100
15%
Value14.7 s
8/100
10%
1842 ms
3097 ms
472 ms
483 ms
976 ms
Our browser made a total of 60 requests to load all elements on the main page. We found that 90% of them (54 requests) were addressed to the original Nav123.com, 2% (1 request) were made to S13.cnzz.com and 2% (1 request) were made to Oz.cnzz.com. The less responsive or slowest element that took the longest time to load (3.4 sec) relates to the external source C.cnzz.com.
Page size can be reduced by 307.8 kB (54%)
566.9 kB
259.1 kB
In fact, the total size of Nav123.com main page is 566.9 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. 15% of websites need less resources to load. Images take 390.2 kB which makes up the majority of the site volume.
Potential reduce by 44.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. This page needs HTML code to be minified as it can gain 7.6 kB, which is 14% 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 44.3 kB or 82% of the original size.
Potential reduce by 160.6 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, Nav 123 needs image optimization as it can save up to 160.6 kB or 41% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 12.0 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 12.0 kB or 60% of the original size.
Potential reduce by 90.9 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. Nav123.com needs all CSS files to be minified and compressed as it can save up to 90.9 kB or 89% of the original size.
Number of requests can be reduced by 18 (31%)
58
40
The browser has sent 58 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Nav 123. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for JavaScripts and as a result speed up the page load time.
index.html
1842 ms
index.css
3097 ms
2.js
472 ms
taiyang.gif
483 ms
language.js
976 ms
sy1.gif
235 ms
home.gif
231 ms
ic_chan.gif
224 ms
xue1.jpg
254 ms
shouye.gif
267 ms
xueli.gif
438 ms
kaoyan.gif
443 ms
jianzhu.gif
457 ms
yishi.gif
463 ms
caikuai.gif
474 ms
yewu.gif
496 ms
qita.gif
656 ms
2010091119414566812.gif
675 ms
pa(1).gif
685 ms
pa(2).gif
690 ms
pa(3).gif
691 ms
pa(4).gif
727 ms
pa(5).gif
875 ms
2010091915271250319.jpg
1344 ms
xxx_01.jpg
967 ms
xxx_03.jpg
967 ms
xxx_06.jpg
969 ms
xxx_07.jpg
964 ms
vvv_01.jpg
1101 ms
vvv_03.jpg
1230 ms
love.gif
1195 ms
menu_s.gif
1438 ms
so_01.jpg
1277 ms
so_02.jpg
1510 ms
so_03.jpg
1371 ms
so_04.jpg
1380 ms
so_05.jpg
1448 ms
so_06.jpg
1994 ms
so_07.jpg
1674 ms
fw1_01.jpg
2488 ms
fw1_02.jpg
2376 ms
stat.php
1291 ms
fw1_03.jpg
1576 ms
fw1_04.jpg
1649 ms
fw1_05.jpg
1795 ms
fw1_06.jpg
2451 ms
fw1_07.jpg
2566 ms
fw1_08.jpg
1841 ms
fw1_09.jpg
2560 ms
fw1_10.jpg
2767 ms
fw1_11.jpg
2242 ms
fw1_12.jpg
3024 ms
fw1_13.jpg
2940 ms
xue5.jpg
2542 ms
footbg.jpg
2377 ms
stat.htm
162 ms
core.php
3390 ms
9.gif
1453 ms
pic.gif
549 ms
app.gif
1326 ms
nav123.com accessibility score
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
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
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
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
nav123.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
nav123.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
Tap targets are not sized appropriately
ZH
N/A
GB2312
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nav123.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 Nav123.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.
nav123.com
Open Graph description is not detected on the main page of Nav 123. 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: