Tools & Wizards About Us
intu.co.uk screenshot

Report Summary

  • 59

    Performance

    Renders faster than
    75% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

intu.co.uk

Shopy - Where Every Product Tells a Story - Shopy

Page Load Speed

4.5 sec in total

First Response

1.1 sec

Resources Loaded

2.9 sec

Page Rendered

482 ms

intu.co.uk screenshot

About Website

Welcome to intu.co.uk homepage info - get ready to check Intu best content for Japan right away, or after learning these important things about intu.co.uk

Interesting products for your space

Visit intu.co.uk

Key Findings

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

Performance Metrics

intu.co.uk performance score

59

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

47/100

10%

LCP (Largest Contentful Paint)

Value5.2 s

23/100

25%

SI (Speed Index)

Value4.1 s

79/100

10%

TBT (Total Blocking Time)

Value350 ms

73/100

30%

CLS (Cumulative Layout Shift)

Value0.013

100/100

15%

TTI (Time to Interactive)

Value8.9 s

34/100

10%

Network Requests Diagram

intu.co.uk

1126 ms

e54737f-b0c5baa.css

245 ms

modernizr@2.8.3,requirejs

9 ms

8d27481807ef22988c384cea9b9903452a2dcd73

164 ms

34a9072-8961870.js

164 ms

Our browser made a total of 40 requests to load all elements on the main page. We found that 50% of them (20 requests) were addressed to the original Intu.co.uk, 10% (4 requests) were made to D33i8j38ri7gad.cloudfront.net and 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Intu.co.uk.

Page Optimization Overview & Recommendations

Page size can be reduced by 743.9 kB (57%)

Content Size

1.3 MB

After Optimization

569.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Intu.co.uk main page is 1.3 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. 55% of websites need less resources to load. Javascripts take 510.2 kB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 180.0 kB

  • Original 200.7 kB
  • After minification 193.8 kB
  • After compression 20.7 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 180.0 kB or 90% of the original size.

Image Optimization

-2%

Potential reduce by 8.3 kB

  • Original 363.9 kB
  • After minification 355.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. Intu images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 350.1 kB

  • Original 510.2 kB
  • After minification 510.1 kB
  • After compression 160.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 350.1 kB or 69% of the original size.

CSS Optimization

-86%

Potential reduce by 205.6 kB

  • Original 238.3 kB
  • After minification 238.1 kB
  • After compression 32.7 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. Intu.co.uk needs all CSS files to be minified and compressed as it can save up to 205.6 kB or 86% of the original size.

Requests Breakdown

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

Requests Now

36

After Optimization

20

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

intu.co.uk

intu.co.uk

1126 ms

e54737f-b0c5baa.css

e54737f-b0c5baa.css

245 ms

modernizr@2.8.3,requirejs

modernizr@2.8.3,requirejs

9 ms

8d27481807ef22988c384cea9b9903452a2dcd73

8d27481807ef22988c384cea9b9903452a2dcd73

164 ms

34a9072-8961870.js

34a9072-8961870.js

164 ms

95dce82-ef4623c.js

95dce82-ef4623c.js

154 ms

gpt.js

gpt.js

69 ms

g

g

69 ms

gtm.js

gtm.js

45 ms

logo_intu_large_header@1x.png

logo_intu_large_header@1x.png

183 ms

intu.core.js

intu.core.js

351 ms

pubads_impl_81.js

pubads_impl_81.js

75 ms

1881949640-0

1881949640-0

124 ms

joysans-regular-webfont.woff

joysans-regular-webfont.woff

240 ms

intu-icons.woff

intu-icons.woff

273 ms

fselliot-bold-webfont.woff

fselliot-bold-webfont.woff

273 ms

analytics.js

analytics.js

31 ms

xtcore.js

xtcore.js

194 ms

ads

ads

59 ms

container.html

container.html

23 ms

collect

collect

6 ms

collect

collect

109 ms

3115687665165268353

3115687665165268353

73 ms

ads

ads

71 ms

anim-loading.gif

anim-loading.gif

155 ms

osd.js

osd.js

24 ms

hit.xiti

hit.xiti

530 ms

session-cookie

session-cookie

275 ms

suggest

suggest

939 ms

slick.min.js

slick.min.js

166 ms

intu.googleanalytics.js

intu.googleanalytics.js

166 ms

mossbros_50fb419addd111e5871802985b99011f.jpg

mossbros_50fb419addd111e5871802985b99011f.jpg

80 ms

mossbros_58809134dc3411e59be802985b99011f.jpg

mossbros_58809134dc3411e59be802985b99011f.jpg

6 ms

mossbros_58b5a6c6dc3411e59be802985b99011f.jpg

mossbros_58b5a6c6dc3411e59be802985b99011f.jpg

9 ms

mossbros_0a7ae180d13811e5aaaa0aa7306b6b64.jpg

mossbros_0a7ae180d13811e5aaaa0aa7306b6b64.jpg

8 ms

hinclude.js

hinclude.js

267 ms

thumb_19058_home_hero_secondary_1x.jpeg

thumb_19058_home_hero_secondary_1x.jpeg

229 ms

thumb_19044_home_hero_secondary_1x.jpeg

thumb_19044_home_hero_secondary_1x.jpeg

379 ms

thumb_19033_home_hero_secondary_1x.jpeg

thumb_19033_home_hero_secondary_1x.jpeg

328 ms

thumb_19057_home_hero_secondary_1x.jpeg

thumb_19057_home_hero_secondary_1x.jpeg

290 ms

Accessibility Review

intu.co.uk accessibility score

63

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.

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

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

intu.co.uk best practices score

83

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

High

Page has valid source maps

SEO Factors

intu.co.uk SEO score

92

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

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

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 Intu.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 Intu.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

intu.co.uk

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