Tools & Wizards About Us
crop.org screenshot

Report Summary

  • 46

    Performance

    Renders faster than
    66% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

crop.org

CROP - Mobilizing Critical Research for Preventing and Eradicating Poverty

Page Load Speed

2.9 sec in total

First Response

238 ms

Resources Loaded

2.4 sec

Page Rendered

293 ms

crop.org screenshot

About Website

Welcome to crop.org homepage info - get ready to check CROP best content for Egypt right away, or after learning these important things about crop.org

Comparative Research Programme on Poverty (CROP) is an international research programme initiated in 1992 by the International Social Science Council. It is now one of the major programmes of the Coun...

Visit crop.org

Key Findings

We analyzed Crop.org page load time and found that the first response time was 238 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

crop.org performance score

46

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

20/100

10%

LCP (Largest Contentful Paint)

Value6.3 s

11/100

25%

SI (Speed Index)

Value5.5 s

55/100

10%

TBT (Total Blocking Time)

Value190 ms

91/100

30%

CLS (Cumulative Layout Shift)

Value0.423

23/100

15%

TTI (Time to Interactive)

Value7.5 s

47/100

10%

Network Requests Diagram

crop.org

238 ms

www.crop.org

680 ms

nivo-slider.css

122 ms

normalize_v3.0.2.css

239 ms

Style.css

363 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 71% of them (30 requests) were addressed to the original Crop.org, 10% (4 requests) were made to Ajax.googleapis.com and 5% (2 requests) were made to Cdn.datatables.net. The less responsive or slowest element that took the longest time to load (743 ms) belongs to the original domain Crop.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 90.2 kB (21%)

Content Size

437.9 kB

After Optimization

347.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Crop.org main page is 437.9 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. 40% of websites need less resources to load. Javascripts take 250.8 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 22.1 kB

  • Original 28.4 kB
  • After minification 25.3 kB
  • After compression 6.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. This page needs HTML code to be minified as it can gain 3.1 kB, which is 11% 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 22.1 kB or 78% of the original size.

Image Optimization

-6%

Potential reduce by 8.9 kB

  • Original 148.2 kB
  • After minification 139.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. CROP images are well optimized though.

JavaScript Optimization

-21%

Potential reduce by 53.5 kB

  • Original 250.8 kB
  • After minification 250.8 kB
  • After compression 197.3 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 53.5 kB or 21% of the original size.

CSS Optimization

-53%

Potential reduce by 5.6 kB

  • Original 10.5 kB
  • After minification 9.2 kB
  • After compression 4.9 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. Crop.org needs all CSS files to be minified and compressed as it can save up to 5.6 kB or 53% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (48%)

Requests Now

40

After Optimization

21

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

crop.org

crop.org

238 ms

www.crop.org

www.crop.org

680 ms

nivo-slider.css

nivo-slider.css

122 ms

normalize_v3.0.2.css

normalize_v3.0.2.css

239 ms

Style.css

Style.css

363 ms

customApiStyle.css

customApiStyle.css

463 ms

jquery.min.js

jquery.min.js

87 ms

jquery.js

jquery.js

119 ms

jquery-ui.css

jquery-ui.css

113 ms

jquery-ui.min.js

jquery-ui.min.js

123 ms

script.js

script.js

564 ms

buttons.js

buttons.js

78 ms

jquery.cycle2.min.js

jquery.cycle2.min.js

108 ms

loadjs.aspx

loadjs.aspx

606 ms

jquery.dataTables.js

jquery.dataTables.js

104 ms

jquery.dataTables.css

jquery.dataTables.css

117 ms

plusone.js

plusone.js

103 ms

script.js

script.js

602 ms

webpath.js

webpath.js

601 ms

confirm.js

confirm.js

603 ms

jquery.lightbox-0.5.js

jquery.lightbox-0.5.js

647 ms

ga.js

ga.js

118 ms

bg_top.gif

bg_top.gif

169 ms

logo-mobile.png

logo-mobile.png

171 ms

twitter.png

twitter.png

171 ms

facebook.png

facebook.png

171 ms

youtube.png

youtube.png

170 ms

menu_icon.png

menu_icon.png

167 ms

logo-m-motto.png

logo-m-motto.png

237 ms

viewimage.aspx

viewimage.aspx

349 ms

viewimage.aspx

viewimage.aspx

241 ms

uib.gif

uib.gif

237 ms

isc_new.png

isc_new.png

238 ms

viewimage.aspx

viewimage.aspx

743 ms

viewimage.aspx

viewimage.aspx

351 ms

viewimage.aspx

viewimage.aspx

352 ms

viewimage.aspx

viewimage.aspx

348 ms

viewimage.aspx

viewimage.aspx

352 ms

viewimage.aspx

viewimage.aspx

464 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

55 ms

__utm.gif

__utm.gif

38 ms

style_print.css

style_print.css

115 ms

Accessibility Review

crop.org accessibility score

68

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<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

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

crop.org best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

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

crop.org SEO score

98

Search Engine Optimization Advices

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

crop.org

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