6.5 sec in total
79 ms
4.2 sec
2.1 sec
Welcome to epec.net homepage info - get ready to check EPEC best content right away, or after learning these important things about epec.net
The Education in Palliative & End-of-Life Care Program educates healthcare professionals on the essential clinical competencies of palliative and end-of-life care.
Visit epec.netWe analyzed Epec.net page load time and found that the first response time was 79 ms and then it took 6.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
epec.net performance score
name
value
score
weighting
Value4.1 s
21/100
10%
Value14.9 s
0/100
25%
Value19.6 s
0/100
10%
Value29,800 ms
0/100
30%
Value0
100/100
15%
Value42.2 s
0/100
10%
79 ms
83 ms
100 ms
133 ms
51 ms
Our browser made a total of 64 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Epec.net, 17% (11 requests) were made to Bioethics.northwestern.edu and 17% (11 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (3 sec) relates to the external source Medtargetsystem.com.
Page size can be reduced by 241.8 kB (8%)
2.9 MB
2.7 MB
In fact, the total size of Epec.net main page is 2.9 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. Images take 2.7 MB which makes up the majority of the site volume.
Potential reduce by 23.3 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 4.1 kB, which is 13% 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 23.3 kB or 75% of the original size.
Potential reduce by 216.9 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. EPEC images are well optimized though.
Potential reduce by 1.5 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.
Potential reduce by 58 B
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. Epec.net has all CSS files already compressed.
Number of requests can be reduced by 25 (48%)
52
27
The browser has sent 52 CSS, Javascripts, AJAX and image requests in order to completely render the main page of EPEC. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
epec.net
79 ms
epec
83 ms
epec
100 ms
epec
133 ms
51 ms
bootstrap.min.css
88 ms
all.css
176 ms
css
99 ms
css
115 ms
landing-page.css
180 ms
widgets.js
143 ms
jquery-3.4.1.min.js
88 ms
popper.min.js
90 ms
bootstrap.min.js
80 ms
slick.min.js
91 ms
common.js
142 ms
beacon.js
219 ms
gtm.js
277 ms
epec-home1440x600.png
459 ms
grey-slash.svg
456 ms
GlobalHealth-150x150.png
456 ms
podcast-icon.svg
450 ms
icon-event-150.png
412 ms
hauser-joshua550x310.png
509 ms
curricula550x310.png
552 ms
diamond-facet-bg.jpg
638 ms
epec-neurology-conference.png
508 ms
epec-pediatrics-logo-150-150.png
551 ms
bullet.png
416 ms
Feinberg-linear-white-240.svg
178 ms
Northwestern_horizontal_white-trimmed.svg
180 ms
lymphomacell-scaled-150x150.jpg
417 ms
widget_iframe.7dae38096d06923d683a2a807172322a.html
210 ms
6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7j.woff
132 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff
143 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVQ.woff
195 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQ.woff
199 ms
fa-solid-900.woff
175 ms
fa-regular-400.woff
277 ms
fa-brands-400.woff
365 ms
121 ms
settings
269 ms
analytics.js
154 ms
js
70 ms
signal.js
125 ms
fp.js
85 ms
linkid.js
64 ms
_itu.png
3025 ms
horizon_timeline.a7991bb824d62c8d5038ddd875db8389.js
36 ms
embeds
32 ms
collect
30 ms
collect
17 ms
collect
41 ms
collect
57 ms
EPEC_Palliative
365 ms
ga-audiences
51 ms
polyfills-57d3feabe8bfd4ee389c.js
28 ms
runtime-eb61dff4a84b8f906e6b.js
55 ms
modules.c7def0268c66f6a548ed.js
104 ms
main-e9db78f5e7b3d83edd5e.js
89 ms
_app-446fb4a338b215deec8c.js
94 ms
%5BscreenName%5D-c8b4c96951cf24f547b4.js
96 ms
_buildManifest.js
101 ms
_ssgManifest.js
102 ms
epec.net 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
epec.net 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
Browser errors were logged to the console
Page has valid source maps
epec.net SEO score
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Epec.net 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 Epec.net 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.
epec.net
Open Graph data is detected on the main page of EPEC. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: