Tools & Wizards About Us
tupian.zjol.com.cn screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

tupian.zjol.com.cn

图片中心_浙江在线-浙江原创新闻图片平台

Page Load Speed

42.4 sec in total

First Response

5.8 sec

Resources Loaded

34.9 sec

Page Rendered

1.7 sec

tupian.zjol.com.cn screenshot

About Website

Welcome to tupian.zjol.com.cn homepage info - get ready to check Tupian Zjol best content for China right away, or after learning these important things about tupian.zjol.com.cn

浙江在线图片中心，以原创新闻图片为主，和浙报集团原创图片库、浙江在线社区论坛紧密联系，每天发布浙江本地最新图片新闻资讯。

Visit tupian.zjol.com.cn

Key Findings

We analyzed Tupian.zjol.com.cn page load time and found that the first response time was 5.8 sec and then it took 36.6 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 30 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

tupian.zjol.com.cn performance score

0

Network Requests Diagram

tupian.zjol.com.cn

5780 ms

photo.zjol.com.cn

1518 ms

picall2013.css

515 ms

picindex2013.css

912 ms

index.css

1252 ms

Our browser made a total of 51 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Tupian.zjol.com.cn, 59% (30 requests) were made to Img.zjolcdn.com and 29% (15 requests) were made to Photo.zjol.com.cn. The less responsive or slowest element that took the longest time to load (20.3 sec) relates to the external source Img.zjolcdn.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 308.1 kB (74%)

Content Size

418.9 kB

After Optimization

110.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Tupian.zjol.com.cn main page is 418.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 246.8 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 28.9 kB

  • Original 34.3 kB
  • After minification 26.7 kB
  • After compression 5.4 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.7 kB, which is 22% 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 28.9 kB or 84% of the original size.

Image Optimization

-76%

Potential reduce by 186.5 kB

  • Original 246.8 kB
  • After minification 60.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. Obviously, Tupian Zjol needs image optimization as it can save up to 186.5 kB or 76% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-65%

Potential reduce by 77.5 kB

  • Original 118.4 kB
  • After minification 113.8 kB
  • After compression 40.9 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 77.5 kB or 65% of the original size.

CSS Optimization

-78%

Potential reduce by 15.2 kB

  • Original 19.4 kB
  • After minification 14.5 kB
  • After compression 4.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. Tupian.zjol.com.cn needs all CSS files to be minified and compressed as it can save up to 15.2 kB or 78% of the original size.

Requests Breakdown

Number of requests can be reduced by 9 (47%)

Requests Now

19

After Optimization

10

  • Images
  • JavaScript
  • CSS

The browser has sent 19 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tupian Zjol. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

tupian.zjol.com.cn

tupian.zjol.com.cn

5780 ms

photo.zjol.com.cn

photo.zjol.com.cn

1518 ms

picall2013.css

picall2013.css

515 ms

picindex2013.css

picindex2013.css

912 ms

index.css

index.css

1252 ms

jquery-1.7.1.min.js

jquery-1.7.1.min.js

7142 ms

jquery.tabso_yeso.js

jquery.tabso_yeso.js

846 ms

tpicall2013.js

tpicall2013.js

1632 ms

tpicindex.js

tpicindex.js

1101 ms

inf.js

inf.js

1329 ms

tjBrowser.js

tjBrowser.js

1821 ms

7368256_658320.jpg

7368256_658320.jpg

20308 ms

tpic2013bg.png

tpic2013bg.png

1306 ms

dots.png

dots.png

427 ms

jb2013.png

jb2013.png

2650 ms

jb2013s.png

jb2013s.png

1953 ms

7368251_908558.jpg

7368251_908558.jpg

20215 ms

7366195_567417.jpg

7366195_567417.jpg

20215 ms

7366194_386315.jpg

7366194_386315.jpg

20204 ms

7360374_827451.jpg

7360374_827451.jpg

20205 ms

7338818_529702.jpg

7338818_529702.jpg

20214 ms

7331297_552563.jpg

7331297_552563.jpg

20225 ms

7326689_130611.jpg

7326689_130611.jpg

20225 ms

7288456_308465.jpg

7288456_308465.jpg

20223 ms

7272665_863285.jpg

7272665_863285.jpg

20226 ms

7368155_246968.jpg

7368155_246968.jpg

20227 ms

7367736_794768.jpg

7367736_794768.jpg

20229 ms

7364628_951507.jpg

7364628_951507.jpg

20231 ms

7363365_923975.jpg

7363365_923975.jpg

20225 ms

7361704_872712.png

7361704_872712.png

20227 ms

7321798_556981.jpg

7321798_556981.jpg

20234 ms

7263249_993073.jpg

7263249_993073.jpg

20233 ms

7263443_624341.jpg

7263443_624341.jpg

20230 ms

7246866_958835.jpg

7246866_958835.jpg

20230 ms

7238669_956264.jpg

7238669_956264.jpg

20231 ms

7367006_878379.jpg

7367006_878379.jpg

20230 ms

7358272_644247.jpg

7358272_644247.jpg

20231 ms

7361705_060693.png

7361705_060693.png

20232 ms

7360541_994938.jpg

7360541_994938.jpg

20232 ms

7356862_956611.jpg

7356862_956611.jpg

20235 ms

7367870_906315.jpg

7367870_906315.jpg

20240 ms

7367849_849987.jpg

7367849_849987.jpg

20235 ms

7367859_426608.jpg

7367859_426608.jpg

20241 ms

7367887_655672.jpg

7367887_655672.jpg

20233 ms

7368037_998243.png

7368037_998243.png

20233 ms

h.js

h.js

927 ms

stats

stats

16115 ms

ta.js

ta.js

16063 ms

hm.gif

hm.gif

861 ms

registerclicks.js

registerclicks.js

681 ms

backtop.png

backtop.png

545 ms

SEO Factors

tupian.zjol.com.cn SEO score

0

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    N/A

  • Encoding

    GB2312

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tupian.zjol.com.cn 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 Tupian.zjol.com.cn 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.

Social Sharing Optimization

tupian.zjol.com.cn

Open Graph description is not detected on the main page of Tupian Zjol. 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: