Tools & Wizards About Us
watchobs.com screenshot

Report Summary

  • 0

    Performance

  • 67

    Accessibility

    Visual factors better than
    that of 32% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 64

    SEO

    Google-friendlier than
    24% of websites

watchobs.com

Watch Observatory by Andre Germain

Page Load Speed

2 sec in total

First Response

269 ms

Resources Loaded

1.1 sec

Page Rendered

645 ms

watchobs.com screenshot

About Website

Visit watchobs.com now to see the best up-to-date Watch Obs content and also check out these interesting facts you probably never knew about watchobs.com

Visit watchobs.com

Key Findings

We analyzed Watchobs.com page load time and found that the first response time was 269 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

watchobs.com performance score

0

Network Requests Diagram

watchobs.com

269 ms

WatchTitle.html

83 ms

WatchBrowser.html

207 ms

WatchViewPort.html

199 ms

StarField1.jpg

127 ms

Our browser made a total of 39 requests to load all elements on the main page. We found that 92% of them (36 requests) were addressed to the original Watchobs.com, 5% (2 requests) were made to Cleardarksky.com and 3% (1 request) were made to C13.statcounter.com. The less responsive or slowest element that took the longest time to load (485 ms) belongs to the original domain Watchobs.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 70.0 kB (10%)

Content Size

713.5 kB

After Optimization

643.5 kB

  • HTML
  • Images
  • JavaScript

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

HTML Optimization

-56%

Potential reduce by 571 B

  • Original 1.0 kB
  • After minification 1.0 kB
  • After compression 446 B

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 571 B or 56% of the original size.

Image Optimization

-5%

Potential reduce by 35.9 kB

  • Original 672.0 kB
  • After minification 636.1 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 Obs images are well optimized though.

JavaScript Optimization

-83%

Potential reduce by 33.5 kB

  • Original 40.5 kB
  • After minification 26.1 kB
  • After compression 7.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 33.5 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 7 (22%)

Requests Now

32

After Optimization

25

  • AJAX
  • Images
  • JavaScript

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

Network Requests Diagram

watchobs.com

watchobs.com

269 ms

WatchTitle.html

WatchTitle.html

83 ms

WatchBrowser.html

WatchBrowser.html

207 ms

WatchViewPort.html

WatchViewPort.html

199 ms

StarField1.jpg

StarField1.jpg

127 ms

watch_logo.gif

watch_logo.gif

281 ms

counter.php

counter.php

89 ms

getcsk.php

getcsk.php

70 ms

Dome_Cam_PanTBN.jpg

Dome_Cam_PanTBN.jpg

238 ms

caldera_sml.jpg

caldera_sml.jpg

247 ms

HDMovies.jpg

HDMovies.jpg

119 ms

DomeTiltPan.jpg

DomeTiltPan.jpg

227 ms

AllSkyCam.jpg

AllSkyCam.jpg

391 ms

AllSkyCam_Horz.jpg

AllSkyCam_Horz.jpg

474 ms

sunmoonimage.gif

sunmoonimage.gif

257 ms

f18_air2.jpg

f18_air2.jpg

355 ms

obj178geo27shd3pg1p5.jpg

obj178geo27shd3pg1p5.jpg

308 ms

WatchWeather.gif

WatchWeather.gif

447 ms

obj19geo23pg1p5_.jpg

obj19geo23pg1p5_.jpg

326 ms

email.jpg

email.jpg

375 ms

TravelGlobe.jpg

TravelGlobe.jpg

406 ms

SpryMenuBar.js

SpryMenuBar.js

418 ms

SpryMenuBarHorizontal.css

SpryMenuBarHorizontal.css

440 ms

ua.js

ua.js

450 ms

ftiens4.js

ftiens4.js

469 ms

demoFramelessNodes.js

demoFramelessNodes.js

485 ms

getcsk.php

getcsk.php

240 ms

StarChart.jpg

StarChart.jpg

128 ms

ftv2vertline.gif

ftv2vertline.gif

68 ms

ftv2mlastnode.gif

ftv2mlastnode.gif

68 ms

ftv2mnode.gif

ftv2mnode.gif

69 ms

ftv2plastnode.gif

ftv2plastnode.gif

70 ms

ftv2pnode.gif

ftv2pnode.gif

71 ms

ftv2blank.gif

ftv2blank.gif

130 ms

ftv2lastnode.gif

ftv2lastnode.gif

131 ms

ftv2node.gif

ftv2node.gif

132 ms

ftv2folderclosed.gif

ftv2folderclosed.gif

132 ms

ftv2folderopen.gif

ftv2folderopen.gif

136 ms

ftv2doc.gif

ftv2doc.gif

134 ms

Accessibility Review

watchobs.com accessibility score

67

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

watchobs.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

watchobs.com SEO score

64

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

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

watchobs.com

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