5.8 sec in total
395 ms
4.3 sec
1.1 sec
Click here to check amazing Project EDWARD content for Portugal. Otherwise, check out these important facts you probably never knew about projectedward.eu
We’re pleased to announce that the Project EDWARD podcast has returned with the new title: My role in The Safe System. For the forthcoming season, we are planning weekly episodes starting Friday 27th...
Visit projectedward.euWe analyzed Projectedward.eu page load time and found that the first response time was 395 ms and then it took 5.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
projectedward.eu performance score
name
value
score
weighting
Value15.0 s
0/100
10%
Value30.7 s
0/100
25%
Value24.2 s
0/100
10%
Value2,550 ms
4/100
30%
Value0.283
43/100
15%
Value35.1 s
0/100
10%
395 ms
2858 ms
320 ms
479 ms
238 ms
Our browser made a total of 48 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Projectedward.eu, 69% (33 requests) were made to Projectedward.org and 10% (5 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2.9 sec) relates to the external source Projectedward.org.
Page size can be reduced by 1.6 MB (81%)
2.0 MB
386.3 kB
In fact, the total size of Projectedward.eu main page is 2.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. 70% of websites need less resources to load. CSS take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 188.2 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 188.2 kB or 87% of the original size.
Potential reduce by 654 B
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. Project EDWARD images are well optimized though.
Potential reduce by 215.2 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 215.2 kB or 67% of the original size.
Potential reduce by 1.2 MB
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. Projectedward.eu needs all CSS files to be minified and compressed as it can save up to 1.2 MB or 86% of the original size.
Number of requests can be reduced by 34 (83%)
41
7
The browser has sent 41 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Project EDWARD. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
projectedward.eu
395 ms
projectedward.org
2858 ms
layerslider.css
320 ms
style.min.css
479 ms
dittyDisplays.css
238 ms
all.css
479 ms
public.min.css
244 ms
gdpr-main-nf.css
472 ms
9c3b828a7da52a05dbfb32d1e651f5f7.min.css
715 ms
jquery.min.js
483 ms
jquery-migrate.min.js
391 ms
layerslider.utils.js
627 ms
layerslider.kreaturamedia.jquery.js
640 ms
layerslider.transitions.js
627 ms
js
59 ms
js
102 ms
classic-10_7.css
16 ms
mc-validate.js
47 ms
rs6.css
328 ms
index.js
324 ms
index.js
405 ms
rbtools.min.js
574 ms
rs6.min.js
790 ms
twitter-widgets.js
472 ms
api.js
39 ms
wp-polyfill-inert.min.js
573 ms
regenerator-runtime.min.js
573 ms
wp-polyfill.min.js
575 ms
index.js
574 ms
smush-lazy-load.min.js
575 ms
main.js
500 ms
330e308d0a2e29f15a63069af501a09a.min.js
618 ms
js
101 ms
analytics.js
96 ms
js
96 ms
js
200 ms
awb-icons.woff
191 ms
fa-solid-900.woff
193 ms
fa-solid-900.ttf
430 ms
fa-regular-400.woff
193 ms
fa-regular-400.ttf
324 ms
widgets.js
311 ms
recaptcha__en.js
161 ms
PE-logo-RBonW-400px.png
267 ms
Podcast-Thumbnail-900x900.png
267 ms
collect
262 ms
collect
261 ms
widget_iframe.2f70fb173b9000da126c79afe2098f02.html
65 ms
projectedward.eu 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
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
projectedward.eu 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
Missing source maps for large first-party JavaScript
projectedward.eu 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
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 Projectedward.eu 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 Projectedward.eu 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.
projectedward.eu
Open Graph data is detected on the main page of Project EDWARD. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: