1.8 sec in total
282 ms
1.4 sec
110 ms
Visit wikigenes.org now to see the best up-to-date Wiki Genes content for Turkey and also check out these interesting facts you probably never knew about wikigenes.org
The world's first wiki where authorship really matters. Due credit and reputation for authors. Imagine a global collaborative knowledge base for original thoughts.
Visit wikigenes.orgWe analyzed Wikigenes.org page load time and found that the first response time was 282 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.
wikigenes.org performance score
name
value
score
weighting
Value2.9 s
54/100
10%
Value3.4 s
68/100
25%
Value4.3 s
75/100
10%
Value620 ms
48/100
30%
Value0.219
57/100
15%
Value6.7 s
56/100
10%
282 ms
257 ms
231 ms
135 ms
138 ms
Our browser made a total of 26 requests to load all elements on the main page. We found that 96% of them (25 requests) were addressed to the original Wikigenes.org, 4% (1 request) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (489 ms) belongs to the original domain Wikigenes.org.
Page size can be reduced by 231.2 kB (70%)
332.5 kB
101.2 kB
In fact, the total size of Wikigenes.org main page is 332.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. 15% of websites need less resources to load. Javascripts take 244.6 kB which makes up the majority of the site volume.
Potential reduce by 25.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 25.6 kB or 72% of the original size.
Potential reduce by 6.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, Wiki Genes needs image optimization as it can save up to 6.2 kB or 23% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 177.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 177.8 kB or 73% of the original size.
Potential reduce by 21.6 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. Wikigenes.org needs all CSS files to be minified and compressed as it can save up to 21.6 kB or 84% of the original size.
Number of requests can be reduced by 10 (42%)
24
14
The browser has sent 24 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wiki Genes. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for JavaScripts and as a result speed up the page load time.
wikigenes.org
282 ms
www.wikigenes.org
257 ms
wokoon_pkg.js
231 ms
locale.js
135 ms
global_pkg.css
138 ms
layoutMain.css
147 ms
search.js
149 ms
bg_shdw_965.gif
71 ms
white_on_red_square_600.png
152 ms
wikigenes.gif
80 ms
headline_flare.gif
75 ms
wikigenes_ref.gif
88 ms
headline.gif
139 ms
email.gif
142 ms
share.gif
153 ms
wikigenes_movie.gif
148 ms
hint.gif
162 ms
society_in_science_logo.gif
209 ms
wikigenes_news_authors.gif
489 ms
mit_logo.gif
216 ms
dig_logo.gif
226 ms
all.js
67 ms
getStatus.json
92 ms
sw_tr.png
89 ms
sw_br.png
88 ms
sw_bl.png
86 ms
wikigenes.org accessibility score
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Form elements do not have associated labels
Links do not have a discernible name
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.
wikigenes.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
Browser errors were logged to the console
wikigenes.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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wikigenes.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 Wikigenes.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.
wikigenes.org
Open Graph data is detected on the main page of Wiki Genes. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: