1.6 sec in total
128 ms
1.4 sec
69 ms
Click here to check amazing Epi Q content. Otherwise, check out these important facts you probably never knew about epi-q.com
EPI-Q is a certified small business providing health economics and outcomes research and population health research services to generate real-world evidence for the Life Sciences Industries.
Visit epi-q.comWe analyzed Epi-q.com page load time and found that the first response time was 128 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
epi-q.com performance score
name
value
score
weighting
Value2.8 s
55/100
10%
Value3.7 s
58/100
25%
Value6.0 s
47/100
10%
Value1,000 ms
27/100
30%
Value0.008
100/100
15%
Value14.0 s
10/100
10%
128 ms
50 ms
49 ms
46 ms
165 ms
Our browser made a total of 50 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Epi-q.com, 40% (20 requests) were made to Static.parastorage.com and 28% (14 requests) were made to Static.wixstatic.com. The less responsive or slowest element that took the longest time to load (474 ms) relates to the external source Static.wixstatic.com.
Page size can be reduced by 322.5 kB (46%)
697.2 kB
374.7 kB
In fact, the total size of Epi-q.com main page is 697.2 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 45% of websites need less resources to load. HTML takes 418.8 kB which makes up the majority of the site volume.
Potential reduce by 317.8 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 317.8 kB or 76% of the original size.
Potential reduce by 537 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. Epi Q images are well optimized though.
Potential reduce by 4.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. This website has mostly compressed JavaScripts.
Number of requests can be reduced by 10 (26%)
38
28
The browser has sent 38 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Epi Q. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and as a result speed up the page load time.
www.epi-q.com
128 ms
minified.js
50 ms
focus-within-polyfill.js
49 ms
polyfill.min.js
46 ms
thunderbolt-commons.8add2233.bundle.min.js
165 ms
main.1550a9c2.bundle.min.js
166 ms
main.renderer.1d21f023.bundle.min.js
164 ms
lodash.min.js
165 ms
react.production.min.js
167 ms
react-dom.production.min.js
170 ms
siteTags.bundle.min.js
168 ms
3873d1_14c886f1e5a44d50a3cb2395123dc3cb~mv2.png
343 ms
bundle.min.js
104 ms
91ce4f25fe39405ba7b358013879d940.jpg
60 ms
3873d1_d61b6faae7a149a2b6b5a5ae502bf8aa~mv2_d_1500_1500_s_2.jpg
298 ms
3873d1_5204e4106ebb4146a91f97bc832a0698~mv2.jpg
358 ms
3873d1_50c4619e0d1e4beb9795c37ed7fb3250~mv2.jpg
261 ms
3873d1_9a17110e69714a848d6515c4add590c0~mv2_d_4912_2028_s_2.jpg
295 ms
3873d1_2b07b1f433234a359c3fc8894d169480~mv2_d_1500_1429_s_2.jpg
274 ms
3873d1_7aa25bb27d624c44b81a0344cb525502~mv2.jpg
474 ms
657d93c686e44e2d9b543a6e1e42cbca.jpg
380 ms
f0af4840c5704569b1bd7daeeb2589a9.jpg
285 ms
62f0fae5d3664613b1ad0874c395a7ca.jpg
289 ms
145 ms
140 ms
151 ms
151 ms
146 ms
146 ms
188 ms
181 ms
189 ms
183 ms
181 ms
181 ms
file.woff
195 ms
file.woff
216 ms
I1Pn3gihk5vyP0Yw5GqKsQ.woff
12 ms
kU6VHbqMAZhaN_nXCmLQsQ.woff
11 ms
file.woff
216 ms
4021a3b9-f782-438b-aeb4-c008109a8b64.woff
22 ms
b56b944e-bbe0-4450-a241-de2125d3e682.woff
11 ms
6f8d1983-4d34-4fa4-9110-988f6c495757.woff
10 ms
deprecation-en.v5.html
6 ms
bolt-performance
33 ms
deprecation-style.v5.css
5 ms
right-arrow.svg
25 ms
WixMadeforDisplay_W_Bd.woff
5 ms
WixMadeforText_W_Bd.woff
5 ms
WixMadeforText_W_Rg.woff
6 ms
epi-q.com accessibility score
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
Buttons do not have an accessible name
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
epi-q.com 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
Page has valid source maps
epi-q.com 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 Epi-q.com 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 Epi-q.com 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.
epi-q.com
Open Graph data is detected on the main page of PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this: