Tools & Wizards About Us
intime.co.uk screenshot

Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

intime.co.uk

In-Time – Watch Repairs, Restoration & Servicing

Page Load Speed

5.6 sec in total

First Response

339 ms

Resources Loaded

5 sec

Page Rendered

223 ms

intime.co.uk screenshot

About Website

Click here to check amazing In Time content for United Kingdom. Otherwise, check out these important facts you probably never knew about intime.co.uk

Visit intime.co.uk

Key Findings

We analyzed Intime.co.uk page load time and found that the first response time was 339 ms and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

intime.co.uk performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.6 s

5/100

10%

LCP (Largest Contentful Paint)

Value9.3 s

1/100

25%

SI (Speed Index)

Value11.6 s

4/100

10%

TBT (Total Blocking Time)

Value960 ms

29/100

30%

CLS (Cumulative Layout Shift)

Value0.078

95/100

15%

TTI (Time to Interactive)

Value16.5 s

5/100

10%

Network Requests Diagram

intime.co.uk

339 ms

436 ms

2505 ms

hide.css

195 ms

select2.css

248 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Intime.co.uk, 85% (50 requests) were made to Thewatchlab.co.uk and 3% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2.5 sec) relates to the external source Thewatchlab.co.uk.

Page Optimization Overview & Recommendations

Page size can be reduced by 271.3 kB (17%)

Content Size

1.6 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Intime.co.uk main page is 1.6 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. 65% of websites need less resources to load. Images take 861.2 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 221.9 kB

  • Original 269.4 kB
  • After minification 265.7 kB
  • After compression 47.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. 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 221.9 kB or 82% of the original size.

Image Optimization

-2%

Potential reduce by 13.8 kB

  • Original 861.2 kB
  • After minification 847.4 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. In Time images are well optimized though.

JavaScript Optimization

-7%

Potential reduce by 32.9 kB

  • Original 450.2 kB
  • After minification 450.2 kB
  • After compression 417.3 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. This website has mostly compressed JavaScripts.

CSS Optimization

-5%

Potential reduce by 2.6 kB

  • Original 51.8 kB
  • After minification 51.4 kB
  • After compression 49.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. Intime.co.uk has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 44 (80%)

Requests Now

55

After Optimization

11

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 55 CSS, Javascripts, AJAX and image requests in order to completely render the main page of In 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 31 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

intime.co.uk

intime.co.uk

339 ms

436 ms

2505 ms

hide.css

hide.css

195 ms

select2.css

select2.css

248 ms

cookie-law-info-public.css

cookie-law-info-public.css

251 ms

cookie-law-info-gdpr.css

cookie-law-info-gdpr.css

252 ms

wp_head.css

wp_head.css

254 ms

style.css

style.css

253 ms

divi-shop-builder-styles.css

divi-shop-builder-styles.css

277 ms

woocommerce-layout.css

woocommerce-layout.css

330 ms

woocommerce.css

woocommerce.css

333 ms

css

css

30 ms

style.min.css

style.min.css

223 ms

wc-realex-redirect.min.css

wc-realex-redirect.min.css

222 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

227 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

244 ms

wp-polyfill.min.js

wp-polyfill.min.js

299 ms

hooks.min.js

hooks.min.js

302 ms

w.js

w.js

28 ms

jquery.min.js

jquery.min.js

387 ms

jquery-migrate.min.js

jquery-migrate.min.js

306 ms

underscore.min.js

underscore.min.js

306 ms

wp-util.min.js

wp-util.min.js

325 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

380 ms

add-to-cart-variation.min.js

add-to-cart-variation.min.js

381 ms

select2.js

select2.js

474 ms

popup.js

popup.js

402 ms

cookie-law-info-public.js

cookie-law-info-public.js

407 ms

js.cookie.min.js

js.cookie.min.js

462 ms

woocommerce.min.js

woocommerce.min.js

464 ms

js

js

80 ms

et-core-unified-8918.min.css

et-core-unified-8918.min.css

468 ms

accounting.min.js

accounting.min.js

549 ms

addons.min.js

addons.min.js

549 ms

sourcebuster.min.js

sourcebuster.min.js

550 ms

order-attribution.min.js

order-attribution.min.js

550 ms

scripts.min.js

scripts.min.js

641 ms

frontend-bundle.min.js

frontend-bundle.min.js

571 ms

frontend-bundle.min.js

frontend-bundle.min.js

571 ms

api.js

api.js

49 ms

common.js

common.js

573 ms

i18n.min.js

i18n.min.js

624 ms

woo-products-filters.min.js

woo-products-filters.min.js

553 ms

wp_footer.js

wp_footer.js

543 ms

g.gif

g.gif

14 ms

gtm.js

gtm.js

69 ms

The-Watch-Lab.png

The-Watch-Lab.png

292 ms

in-time.png

in-time.png

188 ms

repairs-one.png

repairs-one.png

547 ms

repairs-two.png

repairs-two.png

552 ms

repairs-three.png

repairs-three.png

403 ms

twl-logo-w-300x73.png

twl-logo-w-300x73.png

291 ms

twl.png

twl.png

337 ms

font

font

25 ms

modules.woff

modules.woff

344 ms

recaptcha__en.js

recaptcha__en.js

49 ms

woocommerce-smallscreen.css

woocommerce-smallscreen.css

83 ms

style.min.css

style.min.css

86 ms

Accessibility Review

intime.co.uk accessibility score

86

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

intime.co.uk best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

intime.co.uk SEO score

86

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

Social Sharing Optimization

intime.co.uk

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