2.3 sec in total
12 ms
1.9 sec
363 ms
Visit pocketwatchdatabase.com now to see the best up-to-date Pocket Watch Database content for United States and also check out these interesting facts you probably never knew about pocketwatchdatabase.com
Information, serial numbers, specs, and values of American antique pocket watches, with serial number lookups for manufacturers such as Elgin, Illinois, Waltham, and Hamilton.
Visit pocketwatchdatabase.comWe analyzed Pocketwatchdatabase.com page load time and found that the first response time was 12 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
pocketwatchdatabase.com performance score
name
value
score
weighting
Value7.3 s
1/100
10%
Value25.0 s
0/100
25%
Value13.0 s
2/100
10%
Value3,350 ms
2/100
30%
Value0.011
100/100
15%
Value31.6 s
0/100
10%
12 ms
947 ms
64 ms
88 ms
112 ms
Our browser made a total of 99 requests to load all elements on the main page. We found that 47% of them (47 requests) were addressed to the original Pocketwatchdatabase.com, 7% (7 requests) were made to Fonts.gstatic.com and 6% (6 requests) were made to Thumbs4.ebaystatic.com. The less responsive or slowest element that took the longest time to load (947 ms) belongs to the original domain Pocketwatchdatabase.com.
Page size can be reduced by 519.9 kB (26%)
2.0 MB
1.5 MB
In fact, the total size of Pocketwatchdatabase.com main page is 2.0 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. 60% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 76.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 10.0 kB, which is 11% 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 76.5 kB or 87% of the original size.
Potential reduce by 54.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. Pocket Watch Database images are well optimized though.
Potential reduce by 105.2 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 105.2 kB or 67% of the original size.
Potential reduce by 283.6 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. Pocketwatchdatabase.com needs all CSS files to be minified and compressed as it can save up to 283.6 kB or 83% of the original size.
Number of requests can be reduced by 25 (29%)
85
60
The browser has sent 85 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pocket Watch Database. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
pocketwatchdatabase.com
12 ms
pocketwatchdatabase.com
947 ms
jquery-1.11.3.min.js
64 ms
bootstrap.min.css
88 ms
boske.min.css
112 ms
font-awesome.min.css
100 ms
css
135 ms
css
144 ms
css
167 ms
pocketwatchdb.css
95 ms
mosaic.css
54 ms
bootstrap.min.js
97 ms
jquery.autocomplete.js
93 ms
pocketwatchdb.js
94 ms
mosaic.1.0.1.min.js
77 ms
jquery.cycle.all.min.js
125 ms
jquery.cycle.scrubber.js
126 ms
frameScrub.min.js
125 ms
jquery.amaran.min.js
122 ms
show_ads.js
92 ms
insight.min.js
212 ms
pocketwatchdb-print.css
23 ms
gray_jean.png
139 ms
ca-pub-0703468508481644.js
132 ms
zrt_lookup.html
256 ms
show_ads_impl.js
288 ms
140.jpg
714 ms
140.jpg
769 ms
140.jpg
463 ms
140.jpg
665 ms
1
665 ms
140.jpg
458 ms
140.jpg
666 ms
140.jpg
448 ms
140.jpg
459 ms
PWDB-Logo.png
173 ms
PWDB-Logo-Inverse.png
146 ms
question.png
146 ms
low_contrast_linen2.png
175 ms
low_contrast_linen.png
248 ms
elgin96.jpg
324 ms
elgin117.jpg
359 ms
rockford7-18s.jpg
368 ms
elgin372.jpg
415 ms
hamilton992B.jpg
402 ms
elgin50.jpg
418 ms
elgin303.jpg
454 ms
waltham1894-12s.jpg
459 ms
a54c99ca4f5182856c445074f2ba88e3.JPG
466 ms
cf257a83b63c127b94c228e0ca0c387f.JPG
464 ms
07f28292cb134898f06ca31ae8c7cd9f.JPG
472 ms
Default.jpg
464 ms
2e1980e411c0427b676b31bdbad9ab0b.jpg
480 ms
c604f7f5f046cec7d1f29629f78c9843.jpg
481 ms
e2f889246a3ece60ad8fa11214300023.jpg
486 ms
44f9e0076199f90fdbb694e3aca4d767.jpg
487 ms
c166021b39f71d9f0f4def01b5c39cb6.jpg
492 ms
db80a194d463f7cfbd29e6eb2e6f0184.JPG
487 ms
2525848e77fe182a9028a2857f758acd.JPG
498 ms
c640475402a7af1036c3465b4809f6fe.JPG
500 ms
9a9c403dd1a85436948892aec872ff17.JPG
506 ms
741170fed36414e5a7de96e3d205a4ac.JPG
503 ms
cf8cd79dee36f0af6ddca17e4df2d2d8.jpg
510 ms
DoubleSunkDial.jpg
509 ms
progress.gif
509 ms
140.jpg
706 ms
140.jpg
451 ms
140.jpg
451 ms
140.jpg
449 ms
140.jpg
703 ms
140.jpg
704 ms
140.jpg
450 ms
140.jpg
757 ms
jvx_POxM6YeT6dBBhDfmuXYhjbSpvc47ee6xR_80Hnw.ttf
316 ms
F5BSMOSf_T8GT2wiqqpj3SwlidHJgAgmTjOEEzwu1L8.ttf
362 ms
1EqTbJWOZQBfhZ0e3RL9uvesZW2xOQ-xsNqO47m55DA.ttf
411 ms
0DeoTBMnW4sOpD0Zb8OQSALUuEpTyoUstqEm5AMlJo4.ttf
429 ms
jZjuDZSb58pQtWhOr6q-6ALUuEpTyoUstqEm5AMlJo4.ttf
409 ms
ga.js
179 ms
r
83 ms
fontawesome-webfont.woff
53 ms
fontawesome-webfont.woff
436 ms
glyphicons-halflings-regular.woff
35 ms
Q-XbT1m22Fi9BEKb7y59O8DdSZkkecOE1hvV7ZHvhyU.ttf
327 ms
IWi8e5bpnqhMRsZKTcTUWsBaWKZ57bY3RXgXH6dOjZ0.ttf
326 ms
__utm.gif
124 ms
ads
207 ms
osd.js
82 ms
ads
308 ms
490925228055953074
52 ms
abg.js
33 ms
m_js_controller.js
51 ms
googlelogo_color_112x36dp.png
72 ms
fontawesome-webfont.ttf
32 ms
s
43 ms
x_button_blue2.png
45 ms
12824494605421636470
24 ms
E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js
10 ms
fontawesome-webfont.svg
45 ms
pocketwatchdatabase.com accessibility score
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
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.
pocketwatchdatabase.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
pocketwatchdatabase.com SEO score
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pocketwatchdatabase.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Pocketwatchdatabase.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.
pocketwatchdatabase.com
Open Graph description is not detected on the main page of Pocket Watch Database. 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: