3.7 sec in total
976 ms
2.6 sec
134 ms
Click here to check amazing STRING Db content for China. Otherwise, check out these important facts you probably never knew about string-db.org
Visit string-db.orgWe analyzed String-db.org page load time and found that the first response time was 976 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
string-db.org performance score
name
value
score
weighting
Value1.9 s
88/100
10%
Value3.3 s
68/100
25%
Value2.0 s
99/100
10%
Value370 ms
70/100
30%
Value0.122
84/100
15%
Value4.4 s
83/100
10%
976 ms
190 ms
458 ms
190 ms
190 ms
Our browser made a total of 75 requests to load all elements on the main page. We found that 97% of them (73 requests) were addressed to the original String-db.org, 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (976 ms) belongs to the original domain String-db.org.
Page size can be reduced by 465.5 kB (66%)
709.0 kB
243.5 kB
In fact, the total size of String-db.org main page is 709.0 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. 25% of websites need less resources to load. Javascripts take 343.7 kB which makes up the majority of the site volume.
Potential reduce by 195.5 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 195.5 kB or 76% of the original size.
Potential reduce by 3.6 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. STRING Db images are well optimized though.
Potential reduce by 251.0 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 251.0 kB or 73% of the original size.
Potential reduce by 15.4 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. String-db.org needs all CSS files to be minified and compressed as it can save up to 15.4 kB or 84% of the original size.
Number of requests can be reduced by 39 (54%)
72
33
The browser has sent 72 CSS, Javascripts, AJAX and image requests in order to completely render the main page of STRING Db. 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.
string-db.org
976 ms
newstring_scripts_7018.js
190 ms
jquery-1.7.1.min.js
458 ms
basic_js_util_7018.js
190 ms
basic_ajax_7018.js
190 ms
basic_floating_div_7018.js
190 ms
ac_oetags.js
277 ms
floatingDiv.css
276 ms
standard_styles_p.v7266.css
278 ms
prototype.js
555 ms
scriptaculous.js
283 ms
embedded_fonts.css
93 ms
ga.js
37 ms
left_corner_p.png
96 ms
logo_still_p.gif
93 ms
right_corner_p.png
92 ms
fade_left_p.png
92 ms
arrowDownBlack.png
95 ms
ajax-loader.gif
156 ms
genome_context.png
184 ms
experiment_title.png
185 ms
conserved_coexpression.png
186 ms
previous_knowledge.png
188 ms
logo_sib.png
189 ms
logo_CPR.png
247 ms
logo_embl.png
273 ms
fade_right_p.png
275 ms
vertical_background_p.png
268 ms
horizontal_background_left_p.png
269 ms
horizontal_background_right_p.png
269 ms
Folks-Light-webfont.woff
313 ms
Cabin-Bold-webfont.woff
429 ms
tabbase.bottom.png
340 ms
tabbase.lowerleft.png
341 ms
tabselected.upperright.png
342 ms
tabselected.upperleft.png
342 ms
tabselected.lowerright.png
403 ms
tabselected.lowerleft.png
434 ms
tab.upperright.png
436 ms
tab.upperleft.png
434 ms
tab.lowerright.png
436 ms
tab.lowerleft.png
494 ms
tabbase.lowerright.png
519 ms
body.upperright.png
519 ms
body.lowerright.png
521 ms
body.upperleft.png
522 ms
body.lowerleft.png
523 ms
__utm.gif
29 ms
effects.js
533 ms
controls.js
647 ms
button_cogs_off.png
93 ms
button_proteins_on.png
94 ms
normal_button_grey.png
92 ms
submit_button_emph_p.png
93 ms
button_reset_normal.png
92 ms
button_go_proteins.png
92 ms
infoheader.upperright_p.png
173 ms
infoheader.lowerright_p.png
173 ms
infoheader.upperleft_p.png
175 ms
infoheader.lowerleft_p.png
174 ms
infobox.upperright_p.png
176 ms
infobox.lowerright_p.png
181 ms
infobox.upperleft_p.png
263 ms
infobox.lowerleft_p.png
264 ms
tabcoloredbase_p.lowerleft.png
264 ms
tabcoloredselected_p.upperright.png
264 ms
tabcoloredselected_p.upperleft.png
265 ms
tabcoloredselected_p.lowerright.png
272 ms
tabcoloredselected_p.lowerleft.png
352 ms
tabcolored_p.upperright.png
353 ms
tabcolored_p.upperleft.png
354 ms
tabcolored_p.lowerright.png
355 ms
tabcolored_p.lowerleft.png
356 ms
tabcoloredbase_p.bottom.png
361 ms
tabcoloredbase_p.lowerright.png
441 ms
string-db.org accessibility score
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
[id] attributes on active, focusable elements are not unique
string-db.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
string-db.org SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise String-db.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 String-db.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.
string-db.org
Open Graph description is not detected on the main page of STRING Db. 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: