Tools & Wizards About Us
cartagen.org screenshot

Report Summary

  • 62

    Performance

    Renders faster than
    77% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 0

    Best Practices

  • 67

    SEO

    Google-friendlier than
    25% of websites

cartagen.org

Cartagen

Page Load Speed

610 ms in total

First Response

54 ms

Resources Loaded

410 ms

Page Rendered

146 ms

cartagen.org screenshot

About Website

Welcome to cartagen.org homepage info - get ready to check Cartagen best content right away, or after learning these important things about cartagen.org

Visit cartagen.org

Key Findings

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

Performance Metrics

cartagen.org performance score

62

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.8 s

91/100

10%

LCP (Largest Contentful Paint)

Value2.4 s

92/100

25%

SI (Speed Index)

Value3.4 s

89/100

10%

TBT (Total Blocking Time)

Value3,000 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value7.0 s

53/100

10%

Network Requests Diagram

cartagen.org

54 ms

style.css

6 ms

cartagen.js

46 ms

3966967238_7a7bfffac3_s.jpg

168 ms

style.gss

14 ms

Our browser made a total of 17 requests to load all elements on the main page. We found that 76% of them (13 requests) were addressed to the original Cartagen.org, 24% (4 requests) were made to Farm3.static.flickr.com. The less responsive or slowest element that took the longest time to load (226 ms) relates to the external source Farm3.static.flickr.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 8.7 kB (14%)

Content Size

61.3 kB

After Optimization

52.6 kB

  • HTML
  • Images
  • CSS

In fact, the total size of Cartagen.org main page is 61.3 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 50.7 kB which makes up the majority of the site volume.

HTML Optimization

-59%

Potential reduce by 4.5 kB

  • Original 7.5 kB
  • After minification 7.4 kB
  • After compression 3.1 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 4.5 kB or 59% of the original size.

Image Optimization

-4%

Potential reduce by 2.0 kB

  • Original 50.7 kB
  • After minification 48.7 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. Cartagen images are well optimized though.

CSS Optimization

-72%

Potential reduce by 2.2 kB

  • Original 3.1 kB
  • After minification 2.5 kB
  • After compression 868 B

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. Cartagen.org needs all CSS files to be minified and compressed as it can save up to 2.2 kB or 72% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

16

After Optimization

16

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 16 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cartagen. According to our analytics all requests are already optimized.

Network Requests Diagram

cartagen.org

cartagen.org

54 ms

style.css

style.css

6 ms

cartagen.js

cartagen.js

46 ms

3966967238_7a7bfffac3_s.jpg

3966967238_7a7bfffac3_s.jpg

168 ms

style.gss

style.gss

14 ms

park.js

park.js

90 ms

rail.js

rail.js

59 ms

waterway.js

waterway.js

23 ms

primary.js

primary.js

66 ms

secondary.js

secondary.js

151 ms

building.js

building.js

195 ms

area.js

area.js

95 ms

3966975886_15091b990d_s.jpg

3966975886_15091b990d_s.jpg

226 ms

3753496047_fe4565959b_s.jpg

3753496047_fe4565959b_s.jpg

224 ms

3824100955_2f2753c009_s.jpg

3824100955_2f2753c009_s.jpg

224 ms

cartagen.png

cartagen.png

140 ms

spinner.gif

spinner.gif

139 ms

Accessibility Review

cartagen.org accessibility score

74

Accessibility Issues

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.

SEO Factors

cartagen.org SEO score

67

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

cartagen.org

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