Tools & Wizards About Us
prescriber360.com screenshot

Report Summary

  • 93

    Performance

    Renders faster than
    92% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 89% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

prescriber360.com

Connecting Pharma Marketing and HCPs in a Digital First World

Page Load Speed

1.6 sec in total

First Response

38 ms

Resources Loaded

1.2 sec

Page Rendered

364 ms

prescriber360.com screenshot

About Website

Welcome to prescriber360.com homepage info - get ready to check Prescriber 360 best content right away, or after learning these important things about prescriber360.com

Enhance the business of pharma with integrated software and device solutions to bridge sales, clinical, patient journey, analytics and other essential strategic verticals.

Visit prescriber360.com

Key Findings

We analyzed Prescriber360.com page load time and found that the first response time was 38 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.

Performance Metrics

prescriber360.com performance score

93

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

81/100

10%

LCP (Largest Contentful Paint)

Value2.9 s

81/100

25%

SI (Speed Index)

Value2.1 s

99/100

10%

TBT (Total Blocking Time)

Value10 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.035

100/100

15%

TTI (Time to Interactive)

Value2.2 s

99/100

10%

Network Requests Diagram

prescriber360.com

38 ms

www.p360.com

419 ms

gtm.js

82 ms

js

124 ms

iubenda_cs.js

29 ms

Our browser made a total of 39 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Prescriber360.com, 33% (13 requests) were made to Res.cloudinary.com and 26% (10 requests) were made to Cdnp360website.azureedge.net. The less responsive or slowest element that took the longest time to load (700 ms) relates to the external source Cdnp360website.azureedge.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 221.8 kB (68%)

Content Size

327.7 kB

After Optimization

105.9 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Prescriber360.com main page is 327.7 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 259.1 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 210.1 kB

  • Original 259.1 kB
  • After minification 257.7 kB
  • After compression 49.0 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 210.1 kB or 81% of the original size.

Image Optimization

-19%

Potential reduce by 11.6 kB

  • Original 62.1 kB
  • After minification 50.5 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, Prescriber 360 needs image optimization as it can save up to 11.6 kB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-1%

Potential reduce by 37 B

  • Original 6.4 kB
  • After minification 6.4 kB
  • After compression 6.4 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.

Requests Breakdown

Number of requests can be reduced by 18 (53%)

Requests Now

34

After Optimization

16

  • Images
  • JavaScript

The browser has sent 34 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Prescriber 360. 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.

Network Requests Diagram

prescriber360.com

prescriber360.com

38 ms

www.p360.com

www.p360.com

419 ms

gtm.js

gtm.js

82 ms

js

js

124 ms

iubenda_cs.js

iubenda_cs.js

29 ms

iubenda.js

iubenda.js

32 ms

p360_em-sig-logo-2x_opt.png

p360_em-sig-logo-2x_opt.png

347 ms

zing_text_3b14026f8b.webp

zing_text_3b14026f8b.webp

345 ms

1d809bf.js

1d809bf.js

119 ms

afd85b0.js

afd85b0.js

190 ms

0a9e7e9.js

0a9e7e9.js

403 ms

4516022.js

4516022.js

537 ms

39a3c85.js

39a3c85.js

333 ms

zing_full_d6c0b0676e.webp

zing_full_d6c0b0676e.webp

354 ms

Icon_1_502e60f70c.webp

Icon_1_502e60f70c.webp

514 ms

Icon_2_058aeabe7a.webp

Icon_2_058aeabe7a.webp

280 ms

Icon_3_584aa35c1c.webp

Icon_3_584aa35c1c.webp

196 ms

birdzai_logo_2d84e735d2.webp

birdzai_logo_2d84e735d2.webp

451 ms

patient_journey_logo_75705a3280.webp

patient_journey_logo_75705a3280.webp

341 ms

swittons_logo_7cc5cd2b89.webp

swittons_logo_7cc5cd2b89.webp

514 ms

Zing_logo_37cc109cdc.webp

Zing_logo_37cc109cdc.webp

685 ms

P360_icon_sales_f79b518191.webp

P360_icon_sales_f79b518191.webp

586 ms

P360_icon_Patient_Insight_6544b5d4e0.webp

P360_icon_Patient_Insight_6544b5d4e0.webp

508 ms

Swittons_symbol_6a00ab9ab1.webp

Swittons_symbol_6a00ab9ab1.webp

616 ms

p360_logo_circle_421ea32052.webp

p360_logo_circle_421ea32052.webp

689 ms

Zing%20logo.png

Zing%20logo.png

510 ms

P360_icon_sales.png

P360_icon_sales.png

511 ms

P360_icon_PatientInsight.png

P360_icon_PatientInsight.png

522 ms

Swittons_symbol.png

Swittons_symbol.png

571 ms

home_bg_bee3a0922e.webp

home_bg_bee3a0922e.webp

596 ms

sprite.png

sprite.png

571 ms

zing-mobile.png

zing-mobile.png

700 ms

gartner.webp

gartner.webp

694 ms

p360-logo-lg.svg

p360-logo-lg.svg

689 ms

OpenSans-Regular.6c5acfa.woff

OpenSans-Regular.6c5acfa.woff

329 ms

OpenSans-SemiBold.ad9bc43.woff

OpenSans-SemiBold.ad9bc43.woff

297 ms

OpenSans-Bold.eb8f357.woff

OpenSans-Bold.eb8f357.woff

303 ms

insight.min.js

insight.min.js

237 ms

js

js

79 ms

Accessibility Review

prescriber360.com accessibility score

96

Accessibility Issues

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

High

[aria-hidden="true"] elements contain focusable descendents

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Best Practices

prescriber360.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Missing source maps for large first-party JavaScript

SEO Factors

prescriber360.com SEO score

93

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Prescriber360.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 Prescriber360.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.

Social Sharing Optimization

prescriber360.com

Open Graph data is detected on the main page of Prescriber 360. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: