2.8 sec in total
173 ms
2.1 sec
480 ms
Welcome to askforevidence.org homepage info - get ready to check Ask For Evidence best content for United Kingdom right away, or after learning these important things about askforevidence.org
Raise expectations of evidence in public life
Visit askforevidence.orgWe analyzed Askforevidence.org page load time and found that the first response time was 173 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
askforevidence.org performance score
name
value
score
weighting
Value2.5 s
68/100
10%
Value7.0 s
6/100
25%
Value4.1 s
79/100
10%
Value270 ms
82/100
30%
Value0.101
89/100
15%
Value7.1 s
52/100
10%
173 ms
463 ms
528 ms
168 ms
825 ms
Our browser made a total of 38 requests to load all elements on the main page. We found that 92% of them (35 requests) were addressed to the original Askforevidence.org, 5% (2 requests) were made to Google-analytics.com and 3% (1 request) were made to Fast.fonts.net. The less responsive or slowest element that took the longest time to load (860 ms) belongs to the original domain Askforevidence.org.
Page size can be reduced by 615.6 kB (23%)
2.7 MB
2.1 MB
In fact, the total size of Askforevidence.org main page is 2.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. 30% of websites need less resources to load. Images take 1.9 MB which makes up the majority of the site volume.
Potential reduce by 30.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 30.7 kB or 80% of the original size.
Potential reduce by 28.7 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. Ask For Evidence images are well optimized though.
Potential reduce by 360.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 360.3 kB or 67% of the original size.
Potential reduce by 196.0 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. Askforevidence.org needs all CSS files to be minified and compressed as it can save up to 196.0 kB or 85% of the original size.
Number of requests can be reduced by 3 (11%)
28
25
The browser has sent 28 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ask For Evidence. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for JavaScripts and as a result speed up the page load time.
askforevidence.org
173 ms
index
463 ms
application-ea03ecf38f68623a15ac404a836769b3.css
528 ms
modernizr-cbde714343799dda8437bcb3e4d0a03d.js
168 ms
application-f8c0407f1dfbbb0417968657289fd0fc.js
825 ms
afe-logo-25704e833fa0c5bc1d2c5d199860eb5b.png
85 ms
2016_Ask_for_Evidence_Ambassadors.jpg
404 ms
pillow_-_hey_paul_studies.jpg
251 ms
cycling.jpg
577 ms
NHS_choices_edit.png
494 ms
I_heart_evidence.jpg
823 ms
Pint_Flickr2.jpg
419 ms
woman_sleep.jpg
353 ms
sleeping_man.jpg
450 ms
HIV_virus.jpg
646 ms
ask_for_evidence_christmas_resizing_6.jpg
499 ms
mattress_image.jpg
545 ms
sheep.jpg
749 ms
tea_LF.jpg
586 ms
AFE_logo_for_AFE_banner.jpg
633 ms
6512036357_02cdff8580_z-2.jpg
830 ms
afe-logo-white-ce8db2fefc5d081bd1552bbace2baa1a.png
672 ms
SASLogo-d44475bc1f9eaf03d5c5f03a3c86dd84.png
727 ms
analytics.js
20 ms
search-icon-77b9e2eeefc03fa8b3099949224b7d20.png
711 ms
sub-menu-top-border-b392ed233a67edbf9e9c8efa3be0a666.png
736 ms
thumb-triangle-up-5a0fb0a4b94596e59ee792967d521dd7.png
797 ms
read-more-56c846bc9589cf41ba9f58e40b64b37c.png
792 ms
collect
15 ms
OpenSans-Regular-webfont-74c4f2533c4ff767f24f5f316d7d186c.woff
768 ms
OpenSans-Light-webfont-6deac0c8cfe46afd9d3ee7f9b698c5a7.woff
778 ms
OpenSans-Semibold-webfont-070d8408d2c948f985df5ba6761c5fab.woff
829 ms
OpenSans-Bold-webfont-4456e268c02ea4b9aae0b7df306b78e3.woff
842 ms
OpenSans-ExtraBold-webfont-49d11c1946e9314c57811a1a171596f3.woff
859 ms
century_gothic_a13f5d76ed3a-15b00d944bbf575d0c80d49b56b8da40.woff
859 ms
century_gothic_4f345a666324-3a499dcf3d72c99a90bd2ea2374d3dcd.woff
860 ms
fontawesome-webfont-b83782d932b98da1712aaebe1028fa9d.woff
860 ms
trackingCode.js
55 ms
askforevidence.org 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
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
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
askforevidence.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
askforevidence.org 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
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Askforevidence.org 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 Askforevidence.org 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.
askforevidence.org
Open Graph data is detected on the main page of Ask For Evidence. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: