2.3 sec in total
94 ms
2.1 sec
166 ms
Welcome to phrma.org homepage info - get ready to check PhRMA best content for United States right away, or after learning these important things about phrma.org
Home page of PhRMA.org
Visit phrma.orgWe analyzed Phrma.org page load time and found that the first response time was 94 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
phrma.org performance score
name
value
score
weighting
Value4.8 s
11/100
10%
Value18.9 s
0/100
25%
Value12.2 s
3/100
10%
Value1,650 ms
11/100
30%
Value0.105
88/100
15%
Value20.8 s
2/100
10%
94 ms
569 ms
80 ms
175 ms
133 ms
Our browser made a total of 67 requests to load all elements on the main page. We found that 73% of them (49 requests) were addressed to the original Phrma.org, 6% (4 requests) were made to Script.crazyegg.com and 6% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (891 ms) belongs to the original domain Phrma.org.
Page size can be reduced by 391.0 kB (25%)
1.5 MB
1.1 MB
In fact, the total size of Phrma.org main page is 1.5 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. 65% of websites need less resources to load. Javascripts take 914.3 kB which makes up the majority of the site volume.
Potential reduce by 52.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. 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 52.6 kB or 78% of the original size.
Potential reduce by 59.8 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, PhRMA needs image optimization as it can save up to 59.8 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 213.8 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 213.8 kB or 23% of the original size.
Potential reduce by 64.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. Phrma.org needs all CSS files to be minified and compressed as it can save up to 64.8 kB or 34% of the original size.
Number of requests can be reduced by 40 (71%)
56
16
The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of PhRMA. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 37 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
phrma.org
94 ms
phrma.org
569 ms
optimized-min.css
80 ms
optimized-min.css
175 ms
optimized-min.css
133 ms
optimized-min.css
236 ms
jquery.js
183 ms
cookie-management.js
154 ms
bootstrap.js
216 ms
raphael.js
290 ms
usmap.js
290 ms
knockout.js
219 ms
knockoutmapping.js
234 ms
owlcarouselmin.js
289 ms
glossary.js
289 ms
select2.js
289 ms
gsap.js
289 ms
gsapscrolltoplugin.js
389 ms
gsapscrolltrigger.js
390 ms
simplebar.js
392 ms
poppermin.js
390 ms
tippy-bundleumdmin.js
388 ms
jquery-ui-min.js
427 ms
jquery-maskedinputmin.js
446 ms
monthPickermin.js
446 ms
optimized-min.js
711 ms
optimized-min.js
517 ms
optimized-min.js
517 ms
optimized-min.js
517 ms
optimized-min.js
518 ms
optimized-min.js
517 ms
optimized-min.js
518 ms
optimized-min.js
518 ms
optimized-min.js
574 ms
css
68 ms
gtm.js
130 ms
phrma-logo-blue.svg
243 ms
phrma_refresh_home_1600x600_min.png
891 ms
honey-comb-white.svg
242 ms
tile1_min.jpg
650 ms
tile2_min.jpg
605 ms
tile3_min.jpg
650 ms
iStock-537309906.jpeg
651 ms
PhRMA-Foundation---2023_White---Stacked.png
889 ms
Voters_For_Cures_logo.svg
889 ms
MedicineAssistanceTool.png
889 ms
working-for-cures-1280x550.png
887 ms
js
48 ms
destination
440 ms
6614.js
437 ms
insight.min.js
435 ms
pixel.js
432 ms
3981.js
671 ms
ndp.js
787 ms
neusa-next-light-woff.woff
663 ms
neusa-next-regular-woff.woff
725 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
426 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf
662 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf
708 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf
708 ms
neusa-next-medium-woff.woff
725 ms
pharma-org-ttf.ttf
708 ms
rp.gif
215 ms
t2_dcjdwxikh_telemetry
173 ms
ga.js
93 ms
phrma.org.json
41 ms
2e23b996f30aa45a4331ff625e76329e.js
24 ms
phrma.org accessibility score
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-*] attributes do not match their roles
ARIA IDs are not unique
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
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
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
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.
phrma.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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
phrma.org SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
![]()
N/A
N/A
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Phrma.org can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Phrma.org main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
phrma.org
Open Graph description is not detected on the main page of PhRMA. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: