Tools & Wizards About Us
pik3ca-testing.com screenshot

Report Summary

  • 23

    Performance

    Renders faster than
    41% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 76

    SEO

    Google-friendlier than
    35% of websites

pik3ca-testing.com

PIK3CA Mutation Testing in HR+/HER2- mBC | HCP

Page Load Speed

1 sec in total

First Response

132 ms

Resources Loaded

917 ms

Page Rendered

0 ms

pik3ca-testing.com screenshot

About Website

Welcome to pik3ca-testing.com homepage info - get ready to check PIK3CA Testing best content right away, or after learning these important things about pik3ca-testing.com

Learn why, when, and how to test your patients with HR+/HER2- advanced or metastatic breast cancer for a PIK3CA mutation and find testing resources.

Visit pik3ca-testing.com

Key Findings

We analyzed Pik3ca-testing.com page load time and found that the first response time was 132 ms and then it took 917 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

pik3ca-testing.com performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

17/100

10%

LCP (Largest Contentful Paint)

Value6.8 s

7/100

25%

SI (Speed Index)

Value5.7 s

52/100

10%

TBT (Total Blocking Time)

Value2,980 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.133

81/100

15%

TTI (Time to Interactive)

Value13.5 s

11/100

10%

Network Requests Diagram

www.pik3ca-testing.com

132 ms

pik3ca-mutation-testing

326 ms

css2

61 ms

css2

76 ms

variables.css

79 ms

Our browser made a total of 37 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Pik3ca-testing.com, 46% (17 requests) were made to Piqray-hcp.com and 46% (17 requests) were made to Usim.beprod.piqray-hcp.com. The less responsive or slowest element that took the longest time to load (326 ms) relates to the external source Piqray-hcp.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 223.3 kB (29%)

Content Size

781.5 kB

After Optimization

558.3 kB

  • HTML
  • Images
  • CSS

In fact, the total size of Pik3ca-testing.com main page is 781.5 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. 50% of websites need less resources to load. Images take 535.4 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 208.0 kB

  • Original 245.2 kB
  • After minification 245.1 kB
  • After compression 37.2 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 208.0 kB or 85% of the original size.

Image Optimization

-3%

Potential reduce by 15.3 kB

  • Original 535.4 kB
  • After minification 520.2 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. PIK3CA Testing images are well optimized though.

CSS Optimization

-3%

Potential reduce by 29 B

  • Original 904 B
  • After minification 904 B
  • After compression 875 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. Pik3ca-testing.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 17 (49%)

Requests Now

35

After Optimization

18

  • Images
  • JavaScript
  • CSS

The browser has sent 35 CSS, Javascripts, AJAX and image requests in order to completely render the main page of PIK3CA Testing. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

www.pik3ca-testing.com

www.pik3ca-testing.com

132 ms

pik3ca-mutation-testing

pik3ca-mutation-testing

326 ms

css2

css2

61 ms

css2

css2

76 ms

variables.css

variables.css

79 ms

6a9d3a921933c23f.css

6a9d3a921933c23f.css

31 ms

polyfills-c67a75d1b6f99dc8.js

polyfills-c67a75d1b6f99dc8.js

115 ms

jquery-3.6.0.min.js

jquery-3.6.0.min.js

59 ms

swiper-bundle.min.js

swiper-bundle.min.js

60 ms

webpack-42cdea76c8170223.js

webpack-42cdea76c8170223.js

58 ms

framework-5f4595e5518b5600.js

framework-5f4595e5518b5600.js

60 ms

main-5e177f13910846a1.js

main-5e177f13910846a1.js

58 ms

_app-463216df118e839e.js

_app-463216df118e839e.js

102 ms

252f366e-73d4d2ca5f796f77.js

252f366e-73d4d2ca5f796f77.js

93 ms

7d0bf13e-3ea7a283f336d1da.js

7d0bf13e-3ea7a283f336d1da.js

111 ms

105-a3f8d94725c4f0a1.js

105-a3f8d94725c4f0a1.js

98 ms

873-6d53da84d72f5427.js

873-6d53da84d72f5427.js

97 ms

%5B...slug%5D-6492373c0016378a.js

%5B...slug%5D-6492373c0016378a.js

189 ms

_buildManifest.js

_buildManifest.js

196 ms

_ssgManifest.js

_ssgManifest.js

191 ms

piqray-logo.jpg

piqray-logo.jpg

91 ms

piqray-advanced-breast-cancer-header-bar-test-disease-prognosis-desktop.png

piqray-advanced-breast-cancer-header-bar-test-disease-prognosis-desktop.png

183 ms

piqray-advanced-breast-cancer-nccn-icon-desktop-1.svg

piqray-advanced-breast-cancer-nccn-icon-desktop-1.svg

185 ms

pernccnguidlinesimage-1.png

pernccnguidlinesimage-1.png

187 ms

piqray-advanced-breast-cancer-pik3ca-gene-functional-domains-desktop.png

piqray-advanced-breast-cancer-pik3ca-gene-functional-domains-desktop.png

188 ms

piqray-advanced-breast-cancer-multiple-factors-desktop.jpeg

piqray-advanced-breast-cancer-multiple-factors-desktop.jpeg

187 ms

piqray-advanced-breast-cancer-triopack-desktop.jpg

piqray-advanced-breast-cancer-triopack-desktop.jpg

184 ms

piqray-advanced-breast-cancer-qiagen-desktop.png

piqray-advanced-breast-cancer-qiagen-desktop.png

189 ms

piqray-advanced-breast-cancer-pik3ca-mutation-testing-kit-desktop.jpeg

piqray-advanced-breast-cancer-pik3ca-mutation-testing-kit-desktop.jpeg

190 ms

piqray-advanced-breast-cancer-foundation-foundationone-cdx-tissue-based-test-desktop.png

piqray-advanced-breast-cancer-foundation-foundationone-cdx-tissue-based-test-desktop.png

193 ms

piqray-advanced-breast-cancer-foundationone-sample-report.jpg

piqray-advanced-breast-cancer-foundationone-sample-report.jpg

188 ms

screenshot-2023-03-15-at-1.18.31-pm.png

screenshot-2023-03-15-at-1.18.31-pm.png

190 ms

piqray-advanced-breast-cancer-foundationone-lquidcdx-plasma-based-test-desktop.png

piqray-advanced-breast-cancer-foundationone-lquidcdx-plasma-based-test-desktop.png

191 ms

frame-2.png

frame-2.png

191 ms

pik3ca-testing-navigator-brochure-03-1.png

pik3ca-testing-navigator-brochure-03-1.png

191 ms

logo_0%20%281%29.png

logo_0%20%281%29.png

190 ms

web-vitals.min.js

web-vitals.min.js

32 ms

Accessibility Review

pik3ca-testing.com accessibility score

88

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

button, link, and menuitem elements do not have accessible names.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

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

High

Form elements do not have associated labels

Best Practices

pik3ca-testing.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

pik3ca-testing.com SEO score

76

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

Document doesn't have a valid hreflang

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

High

Tap targets are not sized appropriately

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 Pik3ca-testing.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 Pik3ca-testing.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

pik3ca-testing.com

Open Graph description is not detected on the main page of PIK3CA Testing. 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: