Tools & Wizards About Us
watchtalkforum.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

watchtalkforum.com

WatchTalkForum - A Friendly Community For Worldwide Watch Lovers

Page Load Speed

9.6 sec in total

First Response

468 ms

Resources Loaded

8.6 sec

Page Rendered

530 ms

watchtalkforum.com screenshot

About Website

Welcome to watchtalkforum.com homepage info - get ready to check Watch Talk Forum best content for United States right away, or after learning these important things about watchtalkforum.com

Truly informative watch forum to discuss watches and related staff, all in WatchTalkForum.

Visit watchtalkforum.com

Key Findings

We analyzed Watchtalkforum.com page load time and found that the first response time was 468 ms and then it took 9.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

watchtalkforum.com performance score

0

Network Requests Diagram

www.watchtalkforum.com

468 ms

index.php

51 ms

index.php

101 ms

index.php

96 ms

main.js

93 ms

Our browser made a total of 76 requests to load all elements on the main page. We found that 43% of them (33 requests) were addressed to the original Watchtalkforum.com, 26% (20 requests) were made to I2.wp.com and 7% (5 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (4.5 sec) relates to the external source Pcookie.cnzz.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 142.8 kB (16%)

Content Size

886.2 kB

After Optimization

743.4 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Watchtalkforum.com main page is 886.2 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. 50% of websites need less resources to load. Images take 646.2 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 97.5 kB

  • Original 113.0 kB
  • After minification 87.3 kB
  • After compression 15.5 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 25.7 kB, which is 23% 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 97.5 kB or 86% of the original size.

Image Optimization

-3%

Potential reduce by 16.7 kB

  • Original 646.2 kB
  • After minification 629.5 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. Watch Talk Forum images are well optimized though.

JavaScript Optimization

-23%

Potential reduce by 28.6 kB

  • Original 127.0 kB
  • After minification 122.4 kB
  • After compression 98.4 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 28.6 kB or 23% of the original size.

Requests Breakdown

Number of requests can be reduced by 28 (38%)

Requests Now

74

After Optimization

46

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.watchtalkforum.com

www.watchtalkforum.com

468 ms

index.php

index.php

51 ms

index.php

index.php

101 ms

index.php

index.php

96 ms

main.js

main.js

93 ms

ips.status.js

ips.status.js

89 ms

adsbygoogle.js

adsbygoogle.js

6 ms

jquery.min.js

jquery.min.js

65 ms

analytics.js

analytics.js

26 ms

z_stat.php

z_stat.php

759 ms

6_logo.png

6_logo.png

42 ms

transparent.png

transparent.png

39 ms

useropts_arrow.png

useropts_arrow.png

38 ms

f_icon_read.png

f_icon_read.png

39 ms

photo-thumb-172.jpeg

photo-thumb-172.jpeg

40 ms

photo-thumb-326.jpeg

photo-thumb-326.jpeg

39 ms

photo-637.png

photo-637.png

45 ms

photo-thumb-12.jpg

photo-thumb-12.jpg

47 ms

photo-thumb-300.jpg

photo-thumb-300.jpg

50 ms

default_large.png

default_large.png

55 ms

photo-thumb-84.jpeg

photo-thumb-84.jpeg

55 ms

photo-thumb-77.jpg

photo-thumb-77.jpg

55 ms

photo-thumb-202.jpg

photo-thumb-202.jpg

68 ms

photo-thumb-190.jpg

photo-thumb-190.jpg

69 ms

icon_lock.png

icon_lock.png

70 ms

top.png

top.png

74 ms

index.php

index.php

109 ms

3a87b4e0acfdd6fac64e237e06235e53

3a87b4e0acfdd6fac64e237e06235e53

103 ms

collect

collect

17 ms

default_large.png

default_large.png

6 ms

default_large.png

default_large.png

3 ms

default_large.png

default_large.png

5 ms

default_large.png

default_large.png

6 ms

default_large.png

default_large.png

7 ms

default_large.png

default_large.png

7 ms

default_large.png

default_large.png

6 ms

default_large.png

default_large.png

8 ms

default_large.png

default_large.png

8 ms

default_large.png

default_large.png

8 ms

default_large.png

default_large.png

7 ms

default_large.png

default_large.png

8 ms

default_large.png

default_large.png

5 ms

default_large.png

default_large.png

4 ms

default_large.png

default_large.png

4 ms

default_large.png

default_large.png

6 ms

default_large.png

default_large.png

4 ms

default_large.png

default_large.png

3 ms

default_large.png

default_large.png

6 ms

default_large.png

default_large.png

3 ms

stat.htm

stat.htm

163 ms

core.php

core.php

754 ms

9.gif

9.gif

1476 ms

sprite_header.jpg

sprite_header.jpg

203 ms

header_glow_left.png

header_glow_left.png

221 ms

header_border.png

header_border.png

49 ms

sprite_nav.jpg

sprite_nav.jpg

48 ms

sprite_icons.png

sprite_icons.png

59 ms

advanced_search.png

advanced_search.png

49 ms

search_icon.png

search_icon.png

58 ms

sprite_main.jpg

sprite_main.jpg

57 ms

subforum_stem.png

subforum_stem.png

58 ms

ca-pub-2048057987418261.js

ca-pub-2048057987418261.js

82 ms

zrt_lookup.html

zrt_lookup.html

135 ms

show_ads_impl.js

show_ads_impl.js

70 ms

sprite_footer.jpg

sprite_footer.jpg

196 ms

ads

ads

334 ms

osd.js

osd.js

13 ms

m_js_controller.js

m_js_controller.js

36 ms

abg.js

abg.js

60 ms

favicon

favicon

43 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

41 ms

nessie_icon_tiamat_white.png

nessie_icon_tiamat_white.png

36 ms

s

s

18 ms

x_button_blue2.png

x_button_blue2.png

8 ms

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

4 ms

app.gif

app.gif

4536 ms

SEO Factors

watchtalkforum.com SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Watchtalkforum.com can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it does not match the claimed English language. Our system also found out that Watchtalkforum.com 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.

Social Sharing Optimization

watchtalkforum.com

Open Graph data is detected on the main page of Watch Talk Forum. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: