3.3 sec in total
159 ms
2.2 sec
975 ms
Click here to check amazing Web EDI content. Otherwise, check out these important facts you probably never knew about webedi.co.uk
Connect to retailers, wholesalers and distributors in minutes. XEDI’s instant EDI platform automates orders, invoices and shipping docs, and integrates with your ERP.
Visit webedi.co.ukWe analyzed Webedi.co.uk page load time and found that the first response time was 159 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
webedi.co.uk performance score
name
value
score
weighting
Value2.4 s
71/100
10%
Value12.6 s
0/100
25%
Value7.5 s
27/100
10%
Value1,510 ms
14/100
30%
Value0.119
84/100
15%
Value21.8 s
1/100
10%
159 ms
311 ms
146 ms
207 ms
207 ms
Our browser made a total of 66 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Webedi.co.uk, 86% (57 requests) were made to Xedi.com and 6% (4 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Xedi.com.
Page size can be reduced by 1.1 MB (69%)
1.7 MB
524.1 kB
In fact, the total size of Webedi.co.uk main page is 1.7 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. 50% of websites need less resources to load. Javascripts take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 39.6 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.8 kB, which is 23% 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 39.6 kB or 83% of the original size.
Potential reduce by 78.5 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. Obviously, Web EDI needs image optimization as it can save up to 78.5 kB or 36% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 1.0 MB
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 1.0 MB or 76% of the original size.
Potential reduce by 3.8 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. Webedi.co.uk has all CSS files already compressed.
Number of requests can be reduced by 12 (50%)
24
12
The browser has sent 24 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Web EDI. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and as a result speed up the page load time.
webedi.co.uk
159 ms
xedi.com
311 ms
xedi.css
146 ms
bootstrap-grid.min.css
207 ms
bootstrap-pagination.css
207 ms
26e32b2926.js
78 ms
jquery-3.5.1.min.js
343 ms
xedi.js
1710 ms
js
68 ms
js
111 ms
logo-dark.svg
72 ms
resources-article.webp
211 ms
home-banner-person-3.webp
277 ms
home-banner-tesco.webp
210 ms
home-banner-walmart.webp
211 ms
home-banner-sap.webp
262 ms
home-banner-sainsburys.webp
261 ms
background-gradient-purple.webp
467 ms
background-gradient-blue.webp
476 ms
netsuite.webp
319 ms
sap.webp
319 ms
epicor.webp
343 ms
sage-200.webp
386 ms
xero.webp
387 ms
banner-laptop.webp
548 ms
mailbox.webp
454 ms
stages.webp
456 ms
message-track.webp
523 ms
yellow-radial-gradient.webp
729 ms
orange-swoosh-line-right.webp
534 ms
scalable.webp
543 ms
background-gradient-orange.webp
728 ms
security.png
605 ms
purple-swoosh-line-left.webp
611 ms
integration-logos.webp
684 ms
gs1-worldwide.svg
673 ms
256bit-encryption.svg
679 ms
drummond.webp
742 ms
star.webp
748 ms
iso27001.webp
752 ms
Group-413.png
806 ms
cheeky-panda.webp
804 ms
english-cheesecake-company.svg
814 ms
propercorn.webp
814 ms
9BAAAAAQAAAAFtwAAAAAAAAAKABQAHgAyAEYAjACiAL4BFgE2AY4AAAABAAAADAA8AAMAAAAAAAIAAAAAAAAAAAAAAAAAAAAAAAAADgCuAAEAAAAAAAEADQAAAAEAAAAAAAIABwCWAAEAAAAAAAMADQBIAAEAAAAAAAQADQCrAAEAAAAAAAUACwAnAAEAAAAAAAYADQBvAAEAAAAAAAoAGgDSAAMAAQQJAAEAGgANAAMAAQQJAAIADgCdAAMAAQQJAAMAGgBVAAMAAQQJAAQAGgC4AAMAAQQJAAUAFgAyAAMAAQQJAAYAGgB8AAMAAQQJAAoANADsd2ViZmxvdy1pY29ucwB3AGUAYgBmAGwAbwB3AC0AaQBjAG8AbgBzVmVyc2lvbiAxLjAAVgBlAHIAcwBpAG8AbgAgADEALgAwd2ViZmxvdy1pY29ucwB3AGUAYgBmAGwAbwB3AC0AaQBjAG8AbgBzd2ViZmxvdy1pY29ucwB3AGUAYgBmAGwAbwB3AC0AaQBjAG8AbgBzUmVndWxhcgBSAGUAZwB1AGwAYQByd2ViZmxvdy1pY29ucwB3AGUAYgBmAGwAbwB3AC0AaQBjAG8AbgBzRm9udCBnZW5lcmF0ZWQgYnkgSWNvTW9vbi4ARgBvAG4AdAAgAGcAZQBuAGUAcgBhAHQAZQBkACAAYgB5ACAASQBjAG8ATQBvAG8AbgAuAAAAAwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA==
0 ms
PlusJakartaDisplay-Regular.ttf
748 ms
gtm.js
93 ms
PlusJakartaDisplay-Medium.ttf
691 ms
js
71 ms
PlusJakartaDisplay-Light.ttf
669 ms
PlusJakartaDisplay-Bold.ttf
677 ms
PlusJakartaDisplay-Italic.ttf
675 ms
PlusJakartaDisplay-MediumItalic.ttf
638 ms
PlusJakartaDisplay-LightItalic.ttf
664 ms
PlusJakartaDisplay-BoldItalic.ttf
651 ms
tasty-plc.webp
637 ms
dixons_carphone.svg
638 ms
blue-arrow-left.svg
618 ms
blue-arrow-right.svg
620 ms
chevron-down.svg
627 ms
support-person.webp
637 ms
logo-light.svg
569 ms
Twitter.svg
562 ms
Group-400.svg
600 ms
analytics.js
17 ms
collect
4 ms
webedi.co.uk accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
ARIA IDs are not unique
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Image elements do not have [alt] attributes
webedi.co.uk best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
webedi.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
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
![]()
EN
![]()
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Webedi.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 Webedi.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.
webedi.co.uk
Open Graph data is detected on the main page of Web EDI. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: