Tools & Wizards About Us
pollinate.co.uk screenshot

Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

pollinate.co.uk

Pollinate: Reconnecting Banks And Businesses Through Payments

Page Load Speed

3 sec in total

First Response

163 ms

Resources Loaded

2 sec

Page Rendered

788 ms

pollinate.co.uk screenshot

About Website

Click here to check amazing Pollinate content. Otherwise, check out these important facts you probably never knew about pollinate.co.uk

Pollinate gives banks a toolkit of tech solutions to better serve merchants, win market share and reclaim customer primacy.

Visit pollinate.co.uk

Key Findings

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

Performance Metrics

pollinate.co.uk performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

27/100

10%

LCP (Largest Contentful Paint)

Value15.0 s

0/100

25%

SI (Speed Index)

Value9.5 s

11/100

10%

TBT (Total Blocking Time)

Value2,530 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value15.6 s

6/100

10%

Network Requests Diagram

pollinate.co.uk

163 ms

www.pollinate.co.uk

340 ms

www.pollinate.global

440 ms

front.used.css

83 ms

app.min.css

248 ms

Our browser made a total of 53 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Pollinate.co.uk, 72% (38 requests) were made to Pollinate.global and 4% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (521 ms) relates to the external source Pollinate.global.

Page Optimization Overview & Recommendations

Page size can be reduced by 75.0 kB (7%)

Content Size

1.0 MB

After Optimization

938.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pollinate.co.uk main page is 1.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. Javascripts take 454.6 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 73.2 kB

  • Original 90.7 kB
  • After minification 77.7 kB
  • After compression 17.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 13.0 kB, which is 14% 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 73.2 kB or 81% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 430.0 kB
  • After minification 430.0 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. Pollinate images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 1.6 kB

  • Original 454.6 kB
  • After minification 454.5 kB
  • After compression 452.9 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

-0%

Potential reduce by 184 B

  • Original 38.3 kB
  • After minification 38.3 kB
  • After compression 38.1 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. Pollinate.co.uk has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 25 (58%)

Requests Now

43

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

pollinate.co.uk

pollinate.co.uk

163 ms

www.pollinate.co.uk

www.pollinate.co.uk

340 ms

www.pollinate.global

www.pollinate.global

440 ms

front.used.css

front.used.css

83 ms

app.min.css

app.min.css

248 ms

jquery.min.js

jquery.min.js

301 ms

js

js

106 ms

rtafar.local.js

rtafar.local.js

236 ms

app.min.js

app.min.js

418 ms

api.js

api.js

47 ms

lazyload.min.js

lazyload.min.js

243 ms

rtafar.app.min.js

rtafar.app.min.js

415 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

409 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

414 ms

wp-polyfill.min.js

wp-polyfill.min.js

414 ms

dom-ready.min.js

dom-ready.min.js

415 ms

hooks.min.js

hooks.min.js

416 ms

i18n.min.js

i18n.min.js

417 ms

a11y.min.js

a11y.min.js

487 ms

jquery.json.min.js

jquery.json.min.js

488 ms

gravityforms.min.js

gravityforms.min.js

488 ms

utils.min.js

utils.min.js

489 ms

vendor-theme.min.js

vendor-theme.min.js

488 ms

scripts-theme.min.js

scripts-theme.min.js

518 ms

frontend.min.js

frontend.min.js

519 ms

gtm.js

gtm.js

105 ms

MC280x160hp-140x80.png

MC280x160hp-140x80.png

199 ms

relative-bold-pro.woff

relative-bold-pro.woff

272 ms

relative-book-pro.woff

relative-book-pro.woff

272 ms

script.js

script.js

101 ms

insight.min.js

insight.min.js

116 ms

hotjar-3348803.js

hotjar-3348803.js

219 ms

26573632.js

26573632.js

506 ms

26573632.js

26573632.js

233 ms

recaptcha__en.js

recaptcha__en.js

102 ms

FS280x160hp-140x80.png

FS280x160hp-140x80.png

158 ms

IP280x160-hp-140x80.png

IP280x160-hp-140x80.png

158 ms

EFM280x160hp-140x80.png

EFM280x160hp-140x80.png

157 ms

518x1124-mobilerevgoal2.svg

518x1124-mobilerevgoal2.svg

135 ms

Tablet-yourbusiness.svg

Tablet-yourbusiness.svg

384 ms

Alison-Rose-1000x1220-1-500x610.jpg

Alison-Rose-1000x1220-1-500x610.jpg

300 ms

natwest-logo.svg

natwest-logo.svg

217 ms

DynamicsOfTrust.svg

DynamicsOfTrust.svg

220 ms

Data.svg

Data.svg

214 ms

Distribution-eroded.svg

Distribution-eroded.svg

209 ms

P1090195-2560x1440.jpg

P1090195-2560x1440.jpg

521 ms

960x0.jpg-2-500x333.webp

960x0.jpg-2-500x333.webp

305 ms

960x0.jpg-1-279x186.webp

960x0.jpg-1-279x186.webp

294 ms

960x0.jpg-5-279x186.webp

960x0.jpg-5-279x186.webp

320 ms

log

log

405 ms

insight_tag_errors.gif

insight_tag_errors.gif

169 ms

insight_tag_errors.gif

insight_tag_errors.gif

169 ms

li_sync

li_sync

18 ms

Accessibility Review

pollinate.co.uk accessibility score

89

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

Links do not have a discernible name

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

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

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

pollinate.co.uk SEO score

90

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

High

Tap targets are not sized appropriately

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

pollinate.co.uk

Open Graph data is detected on the main page of Pollinate. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: