3.5 sec in total
380 ms
2 sec
1.1 sec
Welcome to propka.org homepage info - get ready to check PROPKA best content for Japan right away, or after learning these important things about propka.org
PROPKA predicts the pKa values of ionizable groups in proteins and protein-ligand complexes based in the 3D structure. - GitHub - jensengroup/propka: PROPKA predicts the pKa values of ionizable groups...
Visit propka.orgWe analyzed Propka.org page load time and found that the first response time was 380 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
propka.org performance score
name
value
score
weighting
Value3.5 s
35/100
10%
Value4.2 s
44/100
25%
Value4.4 s
75/100
10%
Value440 ms
64/100
30%
Value0
100/100
15%
Value6.7 s
57/100
10%
380 ms
687 ms
425 ms
530 ms
458 ms
Our browser made a total of 63 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Propka.org, 73% (46 requests) were made to Github.githubassets.com and 17% (11 requests) were made to Avatars.githubusercontent.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Github.githubassets.com.
Page size can be reduced by 210.5 kB (54%)
389.1 kB
178.6 kB
In fact, the total size of Propka.org main page is 389.1 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. 60% of websites need less resources to load. HTML takes 240.1 kB which makes up the majority of the site volume.
Potential reduce by 202.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. 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 202.3 kB or 84% of the original size.
Potential reduce by 3.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. Obviously, PROPKA needs image optimization as it can save up to 3.2 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 5.0 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. Propka.org has all CSS files already compressed.
Number of requests can be reduced by 44 (72%)
61
17
The browser has sent 61 CSS, Javascripts, AJAX and image requests in order to completely render the main page of PROPKA. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 40 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
propka.org
380 ms
propka
687 ms
light-5178aee0ee76.css
425 ms
dark-217d4f9c8e70.css
530 ms
primer-a8d2a8e3b2d5.css
458 ms
global-8b708e970131.css
530 ms
github-190a6c6b2a2a.css
421 ms
code-3d7b701fc6eb.css
565 ms
wp-runtime-c2f5073b5e45.js
901 ms
vendors-node_modules_manuelpuyol_turbo_dist_turbo_es2017-esm_js-7ca92c8d513d.js
901 ms
vendors-node_modules_stacktrace-parser_dist_stack-trace-parser_esm_js-node_modules_github_bro-d351f6-c1d63d230b29.js
889 ms
environment-b63f7d2aa4d4.js
892 ms
vendors-node_modules_selector-observer_dist_index_esm_js-aefe1cd1c587.js
871 ms
vendors-node_modules_delegated-events_dist_index_js-node_modules_github_details-dialog-elemen-63debe-4a2f37f7419e.js
886 ms
vendors-node_modules_github_auto-complete-element_dist_index_js-node_modules_github_catalyst_-6afc16-accdbcccdc1b.js
957 ms
vendors-node_modules_fzy_js_index_js-node_modules_github_markdown-toolbar-element_dist_index_js-6f74e8e38aad.js
890 ms
vendors-node_modules_github_time-elements_dist_index_js-74b4ec51ce20.js
902 ms
vendors-node_modules_github_file-attachment-element_dist_index_js-node_modules_github_filter--6a5bff-b71ed999fc05.js
920 ms
github-elements-e5f2533960fc.js
962 ms
element-registry-de816de7e8d6.js
942 ms
vendors-node_modules_lit-html_lit-html_js-e954e8c01c93.js
967 ms
vendors-node_modules_github_mini-throttle_dist_index_js-node_modules_primer_behaviors_dist_es-899b47-60b74f01ac2c.js
965 ms
vendors-node_modules_github_paste-markdown_dist_index_esm_js-node_modules_koddsson_textarea-c-586f78-aad0fa01c792.js
981 ms
vendors-node_modules_github_remote-form_dist_index_js-node_modules_scroll-anchoring_dist_scro-5881a7-8cc14636eb0d.js
1032 ms
vendors-node_modules_github_alive-client_dist_index_js-node_modules_github_memoize_dist_esm_i-fab77c-ff9d9fde6bc6.js
966 ms
vendors-node_modules_github_filter-input-element_dist_index_js-node_modules_github_quote-sele-7bbf9f-45d498057c64.js
987 ms
app_assets_modules_github_updatable-content_ts-0a26daf35eaa.js
982 ms
app_assets_modules_github_behaviors_keyboard-shortcuts-helper_ts-app_assets_modules_github_fi-253633-eec667c9b7b7.js
982 ms
app_assets_modules_github_sticky-scroll-into-view_ts-65a620396e37.js
983 ms
app_assets_modules_github_behaviors_task-list_ts-app_assets_modules_github_document-ready_ts--6699ac-3cfe9405695e.js
984 ms
app_assets_modules_github_behaviors_commenting_edit_ts-app_assets_modules_github_behaviors_ht-83c235-106e3ba1cd01.js
984 ms
app_assets_modules_github_behaviors_batch-deferred-content_ts-app_assets_modules_github_behav-dc1370-bfadeaf472f3.js
1028 ms
behaviors-4e862147cf45.js
1054 ms
vendors-node_modules_delegated-events_dist_index_js-node_modules_github_catalyst_lib_index_js-06ff533-b01316754e20.js
980 ms
notifications-global-e71e7f99b10d.js
979 ms
vendors-node_modules_optimizely_optimizely-sdk_dist_optimizely_browser_es_min_js-node_modules-4de5ed-a1d36fafc3a7.js
1022 ms
optimizely-290ece774b76.js
1021 ms
vendors-node_modules_virtualized-list_es_index_js-node_modules_github_template-parts_lib_index_js-17ccfc4926a4.js
1022 ms
1933272
754 ms
68747470733a2f2f636f6465636f762e696f2f67682f6a656e73656e67726f75702f70726f706b612f6272616e63682f6d61737465722f67726170682f62616467652e737667
901 ms
1933272
715 ms
237980
772 ms
12460125
861 ms
1239490
892 ms
2011468
791 ms
1546013
886 ms
79358
886 ms
5457942
886 ms
31376682
819 ms
2752011
859 ms
badge.svg
201 ms
68747470733a2f2f62616467652e667572792e696f2f70792f70726f706b612e737667
745 ms
68747470733a2f2f72656164746865646f63732e6f72672f70726f6a656374732f70726f706b612f62616467652f
948 ms
vendors-node_modules_github_remote-form_dist_index_js-node_modules_delegated-events_dist_inde-911b971-386457f8a637.js
664 ms
app_assets_modules_github_ref-selector_ts-8c0f66968207.js
614 ms
codespaces-827da8fcdd12.js
601 ms
vendors-node_modules_github_mini-throttle_dist_decorators_js-node_modules_github_remote-form_-0102c7-8caa4cfcee48.js
550 ms
vendors-node_modules_github_file-attachment-element_dist_index_js-node_modules_github_filter--705b26-37f0124bb128.js
483 ms
repositories-f20bf0827621.js
231 ms
topic-suggestions-5fa4b287978f.js
247 ms
code-menu-38863eeb396c.js
239 ms
vendors-node_modules_github_remote-form_dist_index_js-node_modules_delegated-events_dist_inde-94fd67-30d1a2e5d8ef.js
237 ms
sessions-57098da4983d.js
234 ms
propka.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-hidden="true"] elements contain focusable descendents
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
propka.org 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
propka.org 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
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 Propka.org 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 Propka.org 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.
propka.org
Open Graph data is detected on the main page of PROPKA. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: