Tools & Wizards About Us
datasur.sr screenshot

Report Summary

  • 36

    Performance

    Renders faster than
    55% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

datasur.sr

Datasur: The first and biggest commercial certified datacenter in Suriname

Page Load Speed

8.2 sec in total

First Response

136 ms

Resources Loaded

7 sec

Page Rendered

1 sec

datasur.sr screenshot

About Website

Click here to check amazing Datasur content for Suriname. Otherwise, check out these important facts you probably never knew about datasur.sr

We deliver reliable and flexible ICT infrastructures from an internationally certified data center in Suriname to safely manage and house business critical applications and data for our customers.​

Visit datasur.sr

Key Findings

We analyzed Datasur.sr page load time and found that the first response time was 136 ms and then it took 8.1 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

datasur.sr performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

18/100

10%

LCP (Largest Contentful Paint)

Value8.8 s

1/100

25%

SI (Speed Index)

Value13.4 s

2/100

10%

TBT (Total Blocking Time)

Value450 ms

62/100

30%

CLS (Cumulative Layout Shift)

Value0.066

97/100

15%

TTI (Time to Interactive)

Value14.4 s

9/100

10%

Network Requests Diagram

datasur.sr

136 ms

datasur.sr

594 ms

style.min.css

307 ms

style.min.css

298 ms

style.min.css

326 ms

Our browser made a total of 117 requests to load all elements on the main page. We found that 86% of them (101 requests) were addressed to the original Datasur.sr, 10% (12 requests) were made to Fonts.gstatic.com and 3% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (5.3 sec) belongs to the original domain Datasur.sr.

Page Optimization Overview & Recommendations

Page size can be reduced by 286.5 kB (28%)

Content Size

1.0 MB

After Optimization

729.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Datasur.sr main page is 1.0 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. 65% of websites need less resources to load. Javascripts take 413.0 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 178.6 kB

  • Original 211.8 kB
  • After minification 211.7 kB
  • After compression 33.2 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 178.6 kB or 84% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 53.3 kB
  • After minification 53.3 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. Datasur images are well optimized though.

JavaScript Optimization

-14%

Potential reduce by 56.6 kB

  • Original 413.0 kB
  • After minification 413.0 kB
  • After compression 356.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 56.6 kB or 14% of the original size.

CSS Optimization

-15%

Potential reduce by 51.4 kB

  • Original 338.3 kB
  • After minification 337.9 kB
  • After compression 286.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. Datasur.sr needs all CSS files to be minified and compressed as it can save up to 51.4 kB or 15% of the original size.

Requests Breakdown

Number of requests can be reduced by 95 (96%)

Requests Now

99

After Optimization

4

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

datasur.sr

datasur.sr

136 ms

datasur.sr

datasur.sr

594 ms

style.min.css

style.min.css

307 ms

style.min.css

style.min.css

298 ms

style.min.css

style.min.css

326 ms

style.min.css

style.min.css

301 ms

style.min.css

style.min.css

303 ms

style.min.css

style.min.css

430 ms

cookie-law-info-public.css

cookie-law-info-public.css

587 ms

cookie-law-info-gdpr.css

cookie-law-info-gdpr.css

580 ms

theme.css

theme.css

591 ms

css

css

46 ms

ekiticons.css

ekiticons.css

611 ms

css

css

46 ms

bootstrap.min.css

bootstrap.min.css

718 ms

magnific-popup.css

magnific-popup.css

852 ms

xs_main.css

xs_main.css

598 ms

blog-style.css

blog-style.css

874 ms

animate.css

animate.css

867 ms

owl.carousel.min.css

owl.carousel.min.css

880 ms

owl.theme.default.min.css

owl.theme.default.min.css

900 ms

jquery-ui.structure.min.css

jquery-ui.structure.min.css

1023 ms

jquery-ui.theme.min.css

jquery-ui.theme.min.css

1162 ms

style.css

style.css

1010 ms

iconfont.css

iconfont.css

1152 ms

font-awesome.min.css

font-awesome.min.css

1178 ms

navigation.min.css

navigation.min.css

1197 ms

gutenberg.css

gutenberg.css

5339 ms

style.css

style.css

1319 ms

gutenberg-custom.css

gutenberg-custom.css

1429 ms

responsive.css

responsive.css

1453 ms

elementor-icons.min.css

elementor-icons.min.css

1462 ms

frontend.min.css

frontend.min.css

1207 ms

swiper.min.css

swiper.min.css

1483 ms

e-swiper.min.css

e-swiper.min.css

1628 ms

post-2602.css

post-2602.css

1581 ms

all.min.css

all.min.css

1748 ms

v4-shims.min.css

v4-shims.min.css

1616 ms

css

css

39 ms

js

js

64 ms

widget-spacer.min.css

widget-spacer.min.css

1359 ms

fadeInUp.min.css

fadeInUp.min.css

1487 ms

widget-heading.min.css

widget-heading.min.css

1578 ms

widget-icon-list.min.css

widget-icon-list.min.css

1336 ms

fadeInLeft.min.css

fadeInLeft.min.css

1336 ms

e-animation-shrink.min.css

e-animation-shrink.min.css

1327 ms

widget-image.min.css

widget-image.min.css

1223 ms

fadeIn.min.css

fadeIn.min.css

1362 ms

widget-text-editor.min.css

widget-text-editor.min.css

1360 ms

widget-image-box.min.css

widget-image-box.min.css

1482 ms

fadeInRight.min.css

fadeInRight.min.css

1482 ms

widget-accordion.min.css

widget-accordion.min.css

1556 ms

e-animation-grow.min.css

e-animation-grow.min.css

1340 ms

widget-divider.min.css

widget-divider.min.css

1227 ms

post-442.css

post-442.css

1380 ms

widget-styles.css

widget-styles.css

1398 ms

responsive.css

responsive.css

1482 ms

fontawesome.min.css

fontawesome.min.css

1480 ms

solid.min.css

solid.min.css

1536 ms

post-3850.css

post-3850.css

1491 ms

post-4277.css

post-4277.css

1265 ms

widget-icon-box.min.css

widget-icon-box.min.css

1135 ms

post-6408.css

post-6408.css

1407 ms

post-4655.css

post-4655.css

1184 ms

widget-social-icons.min.css

widget-social-icons.min.css

1444 ms

apple-webkit.min.css

apple-webkit.min.css

1166 ms

cookie-law-info-table.css

cookie-law-info-table.css

1343 ms

brands.min.css

brands.min.css

1293 ms

jquery.min.js

jquery.min.js

1354 ms

cookie-law-info-public.js

cookie-law-info-public.js

1380 ms

Popup.js

Popup.js

1449 ms

PopupConfig.js

PopupConfig.js

1456 ms

PopupBuilder.js

PopupBuilder.js

1440 ms

v4-shims.min.js

v4-shims.min.js

1472 ms

gtagv4.js

gtagv4.js

1517 ms

lazysizes.min.js

lazysizes.min.js

1580 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

1593 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

1660 ms

wp-polyfill.min.js

wp-polyfill.min.js

1738 ms

hooks.min.js

hooks.min.js

1699 ms

i18n.min.js

i18n.min.js

1748 ms

frontend-script.js

frontend-script.js

1651 ms

widget-scripts.js

widget-scripts.js

1661 ms

navigation.min.js

navigation.min.js

1728 ms

jquery-ui.min.js

jquery-ui.min.js

1815 ms

shuffle-letters.js

shuffle-letters.js

1849 ms

jquery.ajaxchimp.min.js

jquery.ajaxchimp.min.js

1753 ms

wow.min.js

wow.min.js

1824 ms

hostslide.js

hostslide.js

1799 ms

Popper.js

Popper.js

1820 ms

main.js

main.js

1666 ms

bootstrap.min.js

bootstrap.min.js

1677 ms

pminstantpage.min.js

pminstantpage.min.js

1903 ms

make-column-clickable.js

make-column-clickable.js

1893 ms

webpack.runtime.min.js

webpack.runtime.min.js

1882 ms

frontend-modules.min.js

frontend-modules.min.js

1892 ms

core.min.js

core.min.js

1968 ms

frontend.min.js

frontend.min.js

2036 ms

elementor.js

elementor.js

2048 ms

animate-circle.min.js

animate-circle.min.js

1956 ms

elementor.js

elementor.js

1906 ms

footer-bg-1.png

footer-bg-1.png

367 ms

footer-bg.png

footer-bg.png

366 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

242 ms

KFOkCnqEu92Fr1MmgVxIIzc.ttf

KFOkCnqEu92Fr1MmgVxIIzc.ttf

241 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

394 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

395 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

397 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

398 ms

KFOkCnqEu92Fr1Mu51xIIzc.ttf

KFOkCnqEu92Fr1Mu51xIIzc.ttf

397 ms

KFOjCnqEu92Fr1Mu51S7ACc6CsE.ttf

KFOjCnqEu92Fr1Mu51S7ACc6CsE.ttf

398 ms

KFOjCnqEu92Fr1Mu51TjASc6CsE.ttf

KFOjCnqEu92Fr1Mu51TjASc6CsE.ttf

397 ms

KFOiCnqEu92Fr1Mu51QrEzAdKg.ttf

KFOiCnqEu92Fr1Mu51QrEzAdKg.ttf

396 ms

KFOjCnqEu92Fr1Mu51TzBic6CsE.ttf

KFOjCnqEu92Fr1Mu51TzBic6CsE.ttf

398 ms

KFOjCnqEu92Fr1Mu51TLBCc6CsE.ttf

KFOjCnqEu92Fr1Mu51TLBCc6CsE.ttf

399 ms

elementskit.woff

elementskit.woff

398 ms

fa-brands-400.woff

fa-brands-400.woff

754 ms

Accessibility Review

datasur.sr accessibility score

95

Accessibility Issues

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.

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

datasur.sr 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

datasur.sr SEO score

86

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

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 Datasur.sr 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 Datasur.sr 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

datasur.sr

Open Graph data is detected on the main page of Datasur. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: