23.9 sec in total
108 ms
23.1 sec
690 ms
Welcome to tom51.cc homepage info - get ready to check Tom 51 best content for China right away, or after learning these important things about tom51.cc
资源影院—绿色的电影网,家长值得信赖!
Visit tom51.ccWe analyzed Tom51.cc page load time and found that the first response time was 108 ms and then it took 23.8 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 7 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
tom51.cc performance score
name
value
score
weighting
Value2.8 s
57/100
10%
Value14.8 s
0/100
25%
Value8.5 s
18/100
10%
Value3,880 ms
1/100
30%
Value0.235
53/100
15%
Value21.2 s
1/100
10%
108 ms
165 ms
36 ms
130 ms
129 ms
Our browser made a total of 114 requests to load all elements on the main page. We found that 12% of them (14 requests) were addressed to the original Tom51.cc, 35% (40 requests) were made to P.tom51.cc and 32% (37 requests) were made to Pic.kk7.cc. The less responsive or slowest element that took the longest time to load (20.2 sec) relates to the external source Pic.kk7.cc.
Page size can be reduced by 195.0 kB (16%)
1.2 MB
1.0 MB
In fact, the total size of Tom51.cc main page is 1.2 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 970.7 kB which makes up the majority of the site volume.
Potential reduce by 84.2 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 84.2 kB or 86% of the original size.
Potential reduce by 6.9 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. Tom 51 images are well optimized though.
Potential reduce by 94.7 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 94.7 kB or 66% of the original size.
Potential reduce by 9.2 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. Tom51.cc needs all CSS files to be minified and compressed as it can save up to 9.2 kB or 68% of the original size.
Number of requests can be reduced by 22 (21%)
103
81
The browser has sent 103 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tom 51. 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.
tom51.cc
108 ms
www.tom51.cc
165 ms
style.css
36 ms
1.js
130 ms
7.js
129 ms
buttom_01.gif
125 ms
notice.js
170 ms
maomao_index.js
174 ms
iframe_time_list.js
5641 ms
foot.js
168 ms
z_stat.php
4473 ms
427.jpg
406 ms
20101521305769765.jpg
4736 ms
topbg.jpg
149 ms
logo.gif
150 ms
cdbg.gif
148 ms
478.jpg
402 ms
872.jpg
403 ms
863.jpg
407 ms
861.jpg
406 ms
859.jpg
403 ms
103.jpg
461 ms
1224.jpg
462 ms
876.jpg
465 ms
56.jpg
464 ms
1174.jpg
476 ms
722.jpg
462 ms
856.jpg
505 ms
761.jpg
508 ms
72.jpg
520 ms
849.jpg
519 ms
847.jpg
514 ms
803.jpg
516 ms
706.jpg
569 ms
802.jpg
569 ms
792.jpg
579 ms
848.jpg
577 ms
875.jpg
582 ms
874.jpg
571 ms
832.jpg
659 ms
707.jpg
661 ms
758.jpg
679 ms
23.jpg
664 ms
804.jpg
674 ms
621.jpg
664 ms
105.jpg
783 ms
871.jpg
789 ms
868.jpg
794 ms
867.jpg
797 ms
866.jpg
1258 ms
865.jpg
823 ms
1427.jpg
4691 ms
231.jpg
2373 ms
180_77.jpg
9225 ms
553.jpg
20176 ms
303.jpg
7943 ms
2008100301474770073.jpg
4396 ms
205_39.jpg
6438 ms
2266.jpg
11399 ms
161_01.jpg
5852 ms
1040.jpg
7045 ms
2008100301464679831.jpg
9305 ms
2008100301444481515.jpg
7841 ms
9252.jpg
9025 ms
4878.jpg
12236 ms
436.jpg
10998 ms
111_59.jpg
14336 ms
4877.jpg
13911 ms
699.jpg
11791 ms
57_14.jpg
13366 ms
9802.jpg
12556 ms
1720.jpg
20159 ms
8962.jpg
16135 ms
2008122823193789564.jpg
15342 ms
8040.jpg
17125 ms
200912923331310706.jpg
16311 ms
876.jpg
17324 ms
6303.jpg
17307 ms
555.jpg
17277 ms
12_98.jpg
18593 ms
20101418403045642.jpg
20154 ms
3598.jpg
19261 ms
2010121323759898.jpg
19244 ms
176_63.jpg
20153 ms
2008100301373792920.jpg
20153 ms
2010011417282881185.jpg
20154 ms
4587_2412.html
199 ms
4587_2413.html
192 ms
ico_02.gif
12 ms
fl.php
13495 ms
getPosData0
4347 ms
760X90.jpg
347 ms
refer
6249 ms
dot.gif
220 ms
864.jpg
857 ms
63.jpg
530 ms
343.jpg
530 ms
873.jpg
538 ms
20101213204739868.jpg
19803 ms
dot.gif
83 ms
rich03.js
88 ms
4587_2415.html
74 ms
shell_v2.js
1676 ms
stat.htm
161 ms
core.php
546 ms
getPosData0
441 ms
jsapi.uyan.cc
9082 ms
dot.gif
112 ms
close.gif
95 ms
logger.js
1747 ms
bds_s_v2.js
1287 ms
bdsstyle.css
543 ms
l1.gif
497 ms
nopic.gif
754 ms
tom51.cc 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.
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
Form elements do not have associated labels
Links do not have a discernible name
tom51.cc 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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
tom51.cc SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
N/A
N/A
GB2312
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tom51.cc 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 Tom51.cc 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.
tom51.cc
Open Graph description is not detected on the main page of Tom 51. 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: