12.3 sec in total
843 ms
11.2 sec
257 ms
Visit imperialtime.co.uk now to see the best up-to-date Imperial Time content for India and also check out these interesting facts you probably never knew about imperialtime.co.uk
Order luxury watches and Jewellery at Imperial Time. We stock Rolex, Audemars Piguet, Cartier and more. Members of the NAJ, located in London, Hatton Garden.
Visit imperialtime.co.ukWe analyzed Imperialtime.co.uk page load time and found that the first response time was 843 ms and then it took 11.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
imperialtime.co.uk performance score
name
value
score
weighting
Value4.2 s
19/100
10%
Value16.4 s
0/100
25%
Value15.0 s
1/100
10%
Value4,250 ms
1/100
30%
Value0.029
100/100
15%
Value32.2 s
0/100
10%
843 ms
44 ms
189 ms
280 ms
277 ms
Our browser made a total of 196 requests to load all elements on the main page. We found that 80% of them (157 requests) were addressed to the original Imperialtime.co.uk, 6% (11 requests) were made to Fonts.gstatic.com and 2% (4 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (7.2 sec) belongs to the original domain Imperialtime.co.uk.
Page size can be reduced by 552.7 kB (14%)
3.9 MB
3.3 MB
In fact, the total size of Imperialtime.co.uk main page is 3.9 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.9 MB which makes up the majority of the site volume.
Potential reduce by 193.1 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 193.1 kB or 83% of the original size.
Potential reduce by 112.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. Imperial Time images are well optimized though.
Potential reduce by 245.1 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 245.1 kB or 37% of the original size.
Potential reduce by 2.3 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. Imperialtime.co.uk has all CSS files already compressed.
Number of requests can be reduced by 153 (87%)
176
23
The browser has sent 176 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Imperial Time. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 130 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.
imperialtime.co.uk
843 ms
css
44 ms
styles-m.css
189 ms
trustpilot.min.css
280 ms
gallery.css
277 ms
style.css
282 ms
grid-mageplaza.css
280 ms
font-awesome.min.css
288 ms
magnific-popup.css
307 ms
styles-l.css
366 ms
fontawesome-all.css
370 ms
owl.carousel.min.css
372 ms
header-styles.css
464 ms
footer-styles.css
372 ms
main-styles.css
498 ms
imperialtime-styles.css
455 ms
font-awesome.min.css
47 ms
logo.png
457 ms
Imperial_time_mobile_logo.png
457 ms
embed
218 ms
require.js
453 ms
mixins.js
694 ms
requirejs-config.js
695 ms
js
74 ms
js
106 ms
b8d4d60d91d48e5254d4b84416fffdf3.png
693 ms
Jewellary-body-image-3.png
6419 ms
Home-banner-11_1.jpg
771 ms
Rolex_Banner.png
6415 ms
Audemars_Piguet_Banner.png
6419 ms
Cartier_Banner.png
6665 ms
Patek_Philippe_Banner.jpg
769 ms
Rolex_Mobile_Banner.png
7220 ms
Audemars_Mobile_Banner.png
6420 ms
Cartier_Mobile_Banner.png
7163 ms
Patak_Mobile_Banner.png
7185 ms
novuna.png
6698 ms
footer-payment.png
6697 ms
js
32 ms
search.js
3 ms
geometry.js
6 ms
main.js
10 ms
css
18 ms
tspr.png
6418 ms
g-logo.png
6262 ms
live-logo.png
6262 ms
movement-gears-background.jpg
6443 ms
a53mfd2k5r
5713 ms
uwt.js
5710 ms
core.js
96 ms
events.js
5711 ms
fbevents.js
5710 ms
gtm.js
77 ms
tp.widget.bootstrap.min.js
5711 ms
tp.min.js
5713 ms
widget
6168 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
5698 ms
KFOmCnqEu92Fr1Me5Q.ttf
5774 ms
KFOlCnqEu92Fr1MmEU9vAw.ttf
5821 ms
KFOlCnqEu92Fr1MmSU5vAw.ttf
5805 ms
KFOlCnqEu92Fr1MmWUlvAw.ttf
5821 ms
KFOlCnqEu92Fr1MmYUtvAw.ttf
5821 ms
fontawesome-webfont.woff
80 ms
fontawesome-webfont.woff
6521 ms
CodazonFont.woff
6500 ms
opensans-700.woff
6339 ms
opensans-600.woff
6430 ms
opensans-400.woff
6532 ms
opensans-300.woff
6553 ms
KFOkCnqEu92Fr1Mu52xP.ttf
5819 ms
KFOjCnqEu92Fr1Mu51S7ABc9.ttf
5818 ms
KFOjCnqEu92Fr1Mu51TjARc9.ttf
5821 ms
KFOjCnqEu92Fr1Mu51TzBhc9.ttf
5821 ms
KFOjCnqEu92Fr1Mu51TLBBc9.ttf
5821 ms
jquery.js
6576 ms
common.js
6790 ms
ajax-post.js
6592 ms
bootstrap.js
6607 ms
app.js
6607 ms
form-key-provider.js
6621 ms
mage-translation-dictionary.js
6658 ms
add-webp-class-to-body.js
6664 ms
theme.js
6664 ms
themecore.js
6664 ms
cookies.js
6672 ms
mage.js
6713 ms
domReady.js
6747 ms
main.MTcyYmY3Y2UyNQ.js
123 ms
clarity.js
51 ms
adsct
202 ms
adsct
103 ms
website
399 ms
floatbutton1_0uA5KIDjSJBNGPeiRDI3YtNcjWJ9mZsPq48NM5iMzp7_jWYVkIHbMtgrDX_xil60_.css
103 ms
floatbutton1_Thjot1_ijmUDxJNcgVhQgbjvVoqkC76taLNxs5xr2mctXg9qs3uyEWffHAD9jHqf_.js
152 ms
template.js
190 ms
confirm.js
187 ms
widget.js
203 ms
dataPost.js
246 ms
material-theme.js
276 ms
jquery-mixin.js
275 ms
main.js
272 ms
bootstrap.js
275 ms
types.js
286 ms
layout.js
331 ms
text.js
309 ms
smart-keyboard-handler.js
269 ms
has-webp.js
267 ms
cookie-wrapper.js
263 ms
siq_mpWsf52LIPg9mU40fjRdjF6WMUs-Q0VNu4KH07GkhNZGQTRxW2eRyFJLAq9VKCYB_.ttf
20 ms
underscore.js
202 ms
translate.js
248 ms
modal.js
269 ms
version.js
249 ms
wrapper.js
182 ms
knockout.js
284 ms
knockout-es5.js
201 ms
scripts.js
249 ms
engine.js
262 ms
bootstrap.js
263 ms
observable_array.js
267 ms
bound-nodes.js
288 ms
main.js
330 ms
registry.js
297 ms
console-logger.js
293 ms
js-translation.json
271 ms
js.cookie.js
285 ms
modal-popup.html
208 ms
modal-slide.html
262 ms
modal-custom.html
269 ms
key-codes.js
271 ms
core.js
269 ms
z-index.js
291 ms
validation.js
222 ms
knockout-repeat.js
263 ms
knockout-fast-foreach.js
265 ms
observable_source.js
265 ms
renderer.js
266 ms
resizable.js
289 ms
i18n.js
295 ms
scope.js
356 ms
range.js
352 ms
mage-init.js
354 ms
keyboard.js
353 ms
optgroup.js
379 ms
after-render.js
385 ms
autoselect.js
442 ms
datepicker.js
441 ms
outer_click.js
442 ms
fadeVisible.js
447 ms
collapsible.js
471 ms
staticChecked.js
476 ms
simple-checked.js
530 ms
bind-html.js
531 ms
tooltip.js
531 ms
color-picker.js
540 ms
events.js
547 ms
arrays.js
497 ms
compare.js
550 ms
misc.js
543 ms
objects.js
541 ms
strings.js
554 ms
template.js
555 ms
local.js
553 ms
logger.js
549 ms
entry-factory.js
542 ms
console-output-handler.js
541 ms
formatter.js
1516 ms
message-pool.js
1674 ms
levels-pool.js
1485 ms
logger-utils.js
1427 ms
data.js
1244 ms
disable-selection.js
1423 ms
focusable.js
1332 ms
form.js
1402 ms
ie.js
1483 ms
keycode.js
1425 ms
labels.js
1426 ms
jquery-patch.js
1424 ms
plugin.js
1429 ms
safe-active-element.js
1487 ms
safe-blur.js
1482 ms
scroll-parent.js
1425 ms
tabbable.js
1427 ms
unique-id.js
1434 ms
validation.js
1509 ms
class.js
1491 ms
loader.js
1481 ms
async.js
1430 ms
tooltip.html
1429 ms
spectrum.js
1431 ms
tinycolor.js
1506 ms
entry.js
1332 ms
moment.js
452 ms
jquery.validate.js
187 ms
dom-observer.js
92 ms
bindings.js
100 ms
imperialtime.co.uk accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[role] values are not valid
ARIA IDs are not unique
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
<frame> or <iframe> elements do not have a title
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
imperialtime.co.uk best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
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
imperialtime.co.uk 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Imperialtime.co.uk 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 Imperialtime.co.uk 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.
imperialtime.co.uk
Open Graph data is detected on the main page of Imperial Time. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: