Tools & Wizards About Us
yadsti.org screenshot

Report Summary

  • 14

    Performance

    Renders faster than
    26% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

yadsti.org

(YADSTI) Youth Agency for Development of Science, Technology & Innovation

Page Load Speed

10.9 sec in total

First Response

2.6 sec

Resources Loaded

8 sec

Page Rendered

276 ms

yadsti.org screenshot

About Website

Visit yadsti.org now to see the best up-to-date YADSTI content and also check out these interesting facts you probably never knew about yadsti.org

(YADSTI) is an initiative of young scientists whose goal is to engage youth in promoting Science, Technology & Innovation (STI) as a tool for development

Visit yadsti.org

Key Findings

We analyzed Yadsti.org page load time and found that the first response time was 2.6 sec and then it took 8.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

yadsti.org performance score

14

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value20.4 s

0/100

10%

LCP (Largest Contentful Paint)

Value23.1 s

0/100

25%

SI (Speed Index)

Value22.4 s

0/100

10%

TBT (Total Blocking Time)

Value640 ms

46/100

30%

CLS (Cumulative Layout Shift)

Value1.386

0/100

15%

TTI (Time to Interactive)

Value30.7 s

0/100

10%

Network Requests Diagram

www.yadsti.org

2573 ms

css

121 ms

css

194 ms

style.css

391 ms

twitter-feed.css

158 ms

Our browser made a total of 67 requests to load all elements on the main page. We found that 55% of them (37 requests) were addressed to the original Yadsti.org, 4% (3 requests) were made to Facebook.com and 4% (3 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Yadsti.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 543.1 kB (49%)

Content Size

1.1 MB

After Optimization

557.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Yadsti.org main page is 1.1 MB. 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 436.2 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 46.0 kB

  • Original 57.4 kB
  • After minification 47.9 kB
  • After compression 11.4 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. This page needs HTML code to be minified as it can gain 9.5 kB, which is 17% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 46.0 kB or 80% of the original size.

Image Optimization

-13%

Potential reduce by 57.4 kB

  • Original 436.2 kB
  • After minification 378.8 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, YADSTI needs image optimization as it can save up to 57.4 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-66%

Potential reduce by 275.4 kB

  • Original 416.8 kB
  • After minification 383.0 kB
  • After compression 141.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 275.4 kB or 66% of the original size.

CSS Optimization

-86%

Potential reduce by 164.2 kB

  • Original 190.2 kB
  • After minification 154.6 kB
  • After compression 26.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. Yadsti.org needs all CSS files to be minified and compressed as it can save up to 164.2 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 41 (65%)

Requests Now

63

After Optimization

22

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.yadsti.org

www.yadsti.org

2573 ms

css

css

121 ms

css

css

194 ms

style.css

style.css

391 ms

twitter-feed.css

twitter-feed.css

158 ms

media-queries.css

media-queries.css

319 ms

flexslider.css

flexslider.css

159 ms

prettyPhoto.css

prettyPhoto.css

325 ms

jquery.ui.all.css

jquery.ui.all.css

156 ms

custom.css

custom.css

312 ms

jquery.js

jquery.js

1723 ms

jquery-migrate.min.js

jquery-migrate.min.js

484 ms

jquery.prettyPhoto.js

jquery.prettyPhoto.js

475 ms

jquery.validate.min.js

jquery.validate.min.js

479 ms

jquery.form.js

jquery.form.js

514 ms

jquery.cycle.lite.js

jquery.cycle.lite.js

460 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

515 ms

jquery.flexslider-min.js

jquery.flexslider-min.js

521 ms

jquery.isotope.min.js

jquery.isotope.min.js

527 ms

core.min.js

core.min.js

456 ms

datepicker.min.js

datepicker.min.js

554 ms

custom.js

custom.js

482 ms

widgets.js

widgets.js

826 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

171 ms

jquery.ui.base.css

jquery.ui.base.css

169 ms

jquery.ui.theme.css

jquery.ui.theme.css

172 ms

jquery.ui.core.css

jquery.ui.core.css

75 ms

jquery.ui.datepicker.css

jquery.ui.datepicker.css

71 ms

button.js

button.js

1091 ms

analytics.js

analytics.js

1030 ms

y1Hbe2RX_normal.jpeg

y1Hbe2RX_normal.jpeg

1291 ms

YADSTIwebLogo1.png

YADSTIwebLogo1.png

811 ms

search-icon.png

search-icon.png

942 ms

YADSTI-ATPS-980x344.jpg

YADSTI-ATPS-980x344.jpg

807 ms

YADSTI-Collaboration-Frameworks-Workshop-Naivasha.jpg

YADSTI-Collaboration-Frameworks-Workshop-Naivasha.jpg

565 ms

YADSTI-Mau-980x344.jpg

YADSTI-Mau-980x344.jpg

768 ms

YADSTI-conference-980x344.jpg

YADSTI-conference-980x344.jpg

558 ms

agricultureHUB.jpg

agricultureHUB.jpg

629 ms

ictHUB.jpg

ictHUB.jpg

609 ms

EngineeringHUB.jpg

EngineeringHUB.jpg

642 ms

HealthandlifesciencesHUB.jpg

HealthandlifesciencesHUB.jpg

652 ms

EnvironmentalHUB.jpg

EnvironmentalHUB.jpg

669 ms

footer-bullit.png

footer-bullit.png

676 ms

s-BiyweUPV0v-yRb-cjciC3USBnSvpkopQaUR-2r7iU.ttf

s-BiyweUPV0v-yRb-cjciC3USBnSvpkopQaUR-2r7iU.ttf

270 ms

all.js

all.js

253 ms

button.71000885400e222c3c0eec823f8f93f0.js

button.71000885400e222c3c0eec823f8f93f0.js

106 ms

252 ms

xd_arbiter.php

xd_arbiter.php

193 ms

xd_arbiter.php

xd_arbiter.php

239 ms

follow_button.fd774b599f565016d763dd860cb31c79.en.html

follow_button.fd774b599f565016d763dd860cb31c79.en.html

174 ms

jot

jot

119 ms

collect

collect

22 ms

dc.js

dc.js

147 ms

button.css

button.css

51 ms

services.css

services.css

13 ms

jquery.min.js

jquery.min.js

129 ms

__utm.gif

__utm.gif

25 ms

ping

ping

69 ms

tag0

tag0

317 ms

px.js

px.js

141 ms

pixel

pixel

317 ms

like.php

like.php

156 ms

Sh_BYjerrZ8.js

Sh_BYjerrZ8.js

365 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

396 ms

pixel

pixel

55 ms

ca.png

ca.png

530 ms

ca.png

ca.png

644 ms

Accessibility Review

yadsti.org accessibility score

81

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

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

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

yadsti.org 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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

yadsti.org SEO score

85

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

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

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 Yadsti.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 Yadsti.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.

Social Sharing Optimization

yadsti.org

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