Tools & Wizards About Us
datasur.sr screenshot

Report Summary

  • 31

    Performance

    Renders faster than
    51% 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

14.1 sec in total

First Response

639 ms

Resources Loaded

12.7 sec

Page Rendered

727 ms

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 639 ms and then it took 13.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

datasur.sr performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.9 s

10/100

10%

LCP (Largest Contentful Paint)

Value9.6 s

0/100

25%

SI (Speed Index)

Value10.9 s

6/100

10%

TBT (Total Blocking Time)

Value780 ms

38/100

30%

CLS (Cumulative Layout Shift)

Value0.053

98/100

15%

TTI (Time to Interactive)

Value9.5 s

30/100

10%

Network Requests Diagram

datasur.sr

639 ms

frontend.min.css

673 ms

post-3850.css

465 ms

post-4655.css

414 ms

style.min.css

461 ms

Our browser made a total of 119 requests to load all elements on the main page. We found that 83% of them (99 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 (10.2 sec) belongs to the original domain Datasur.sr.

Page Optimization Overview & Recommendations

Page size can be reduced by 391.5 kB (29%)

Content Size

1.3 MB

After Optimization

952.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-84%

Potential reduce by 175.7 kB

  • Original 210.5 kB
  • After minification 210.4 kB
  • After compression 34.7 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 175.7 kB or 84% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 270.5 kB
  • After minification 270.5 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

-23%

Potential reduce by 95.4 kB

  • Original 410.2 kB
  • After minification 409.9 kB
  • After compression 314.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 95.4 kB or 23% of the original size.

CSS Optimization

-27%

Potential reduce by 120.3 kB

  • Original 453.0 kB
  • After minification 450.6 kB
  • After compression 332.7 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 120.3 kB or 27% of the original size.

Requests Breakdown

Number of requests can be reduced by 94 (94%)

Requests Now

100

After Optimization

6

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 100 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 39 to 1 for JavaScripts and from 57 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

datasur.sr

datasur.sr

639 ms

frontend.min.css

frontend.min.css

673 ms

post-3850.css

post-3850.css

465 ms

post-4655.css

post-4655.css

414 ms

style.min.css

style.min.css

461 ms

style.min.css

style.min.css

617 ms

style.min.css

style.min.css

484 ms

style.min.css

style.min.css

818 ms

style.min.css

style.min.css

905 ms

styles.css

styles.css

888 ms

cookie-law-info-public.css

cookie-law-info-public.css

1034 ms

cookie-law-info-gdpr.css

cookie-law-info-gdpr.css

1054 ms

theme.css

theme.css

1218 ms

css

css

34 ms

font-awesome.min.css

font-awesome.min.css

1455 ms

jquery-ui.css

jquery-ui.css

1362 ms

simple-job-board-public.css

simple-job-board-public.css

1579 ms

sbttb-fonts.css

sbttb-fonts.css

1419 ms

smooth-back-to-top-button.css

smooth-back-to-top-button.css

1444 ms

tlpportfolio.css

tlpportfolio.css

1598 ms

portfolio-sc.css

portfolio-sc.css

1761 ms

cf7mls.css

cf7mls.css

1805 ms

animate.min.css

animate.min.css

1853 ms

style.css

style.css

1875 ms

ekiticons.css

ekiticons.css

2462 ms

default.css

default.css

1993 ms

elementor-icons.min.css

elementor-icons.min.css

1918 ms

swiper.min.css

swiper.min.css

2241 ms

post-2602.css

post-2602.css

2257 ms

all.min.css

all.min.css

2373 ms

v4-shims.min.css

v4-shims.min.css

2306 ms

post-442.css

post-442.css

2393 ms

css

css

44 ms

bootstrap.min.css

bootstrap.min.css

2813 ms

magnific-popup.css

magnific-popup.css

2722 ms

xs_main.css

xs_main.css

2715 ms

blog-style.css

blog-style.css

2791 ms

css

css

47 ms

js

js

56 ms

animate.css

animate.css

2716 ms

owl.carousel.min.css

owl.carousel.min.css

2444 ms

owl.theme.default.min.css

owl.theme.default.min.css

2661 ms

jquery-ui.structure.min.css

jquery-ui.structure.min.css

2711 ms

jquery-ui.theme.min.css

jquery-ui.theme.min.css

2705 ms

style.css

style.css

2573 ms

iconfont.css

iconfont.css

2559 ms

font-awesome.min.css

font-awesome.min.css

2478 ms

navigation.min.css

navigation.min.css

2378 ms

gutenberg.css

gutenberg.css

10162 ms

style.css

style.css

2836 ms

gutenberg-custom.css

gutenberg-custom.css

2543 ms

responsive.css

responsive.css

2587 ms

widget-styles.css

widget-styles.css

3176 ms

responsive.css

responsive.css

2384 ms

fontawesome.min.css

fontawesome.min.css

2538 ms

brands.min.css

brands.min.css

2577 ms

solid.min.css

solid.min.css

2725 ms

post-4277.css

post-4277.css

2622 ms

post-6408.css

post-6408.css

2759 ms

cookie-law-info-table.css

cookie-law-info-table.css

2724 ms

animations.min.css

animations.min.css

2509 ms

jquery.min.js

jquery.min.js

3250 ms

jquery-migrate.min.js

jquery-migrate.min.js

2776 ms

redirect_method.js

redirect_method.js

2819 ms

cookie-law-info-public.js

cookie-law-info-public.js

2816 ms

Popup.js

Popup.js

2703 ms

PopupConfig.js

PopupConfig.js

2825 ms

PopupBuilder.js

PopupBuilder.js

2853 ms

v4-shims.min.js

v4-shims.min.js

2845 ms

lazysizes.min.js

lazysizes.min.js

3043 ms

index.js

index.js

2998 ms

index.js

index.js

2797 ms

smooth-back-to-top-button.js

smooth-back-to-top-button.js

2822 ms

cf7mls.js

cf7mls.js

2841 ms

frontend-script.js

frontend-script.js

3057 ms

widget-scripts.js

widget-scripts.js

3015 ms

jquery.magnific-popup.min.js

jquery.magnific-popup.min.js

3088 ms

navigation.min.js

navigation.min.js

2532 ms

jquery-ui.min.js

jquery-ui.min.js

3086 ms

tweetie.js

tweetie.js

2858 ms

owl.carousel.min.js

owl.carousel.min.js

3031 ms

shuffle-letters.js

shuffle-letters.js

3019 ms

jquery.ajaxchimp.min.js

jquery.ajaxchimp.min.js

3116 ms

wow.min.js

wow.min.js

3158 ms

hostslide.js

hostslide.js

3057 ms

Popper.js

Popper.js

3058 ms

main.js

main.js

2944 ms

bootstrap.min.js

bootstrap.min.js

3353 ms

make-column-clickable.js

make-column-clickable.js

2909 ms

webpack.runtime.min.js

webpack.runtime.min.js

2989 ms

frontend-modules.min.js

frontend-modules.min.js

3088 ms

waypoints.min.js

waypoints.min.js

2906 ms

core.min.js

core.min.js

3004 ms

frontend.min.js

frontend.min.js

3042 ms

elementor.js

elementor.js

3101 ms

animate-circle.min.js

animate-circle.min.js

3005 ms

elementor.js

elementor.js

3104 ms

Final_HPR8552-scaled.jpg

Final_HPR8552-scaled.jpg

762 ms

footer-bg.png

footer-bg.png

611 ms

analytics.js

analytics.js

241 ms

js

js

237 ms

KFOlCnqEu92Fr1MmSU5fBBc-.woff

KFOlCnqEu92Fr1MmSU5fBBc-.woff

238 ms

KFOkCnqEu92Fr1MmgVxIIzQ.woff

KFOkCnqEu92Fr1MmgVxIIzQ.woff

238 ms

KFOmCnqEu92Fr1Mu4mxM.woff

KFOmCnqEu92Fr1Mu4mxM.woff

479 ms

KFOlCnqEu92Fr1MmEU9fBBc-.woff

KFOlCnqEu92Fr1MmEU9fBBc-.woff

509 ms

KFOlCnqEu92Fr1MmWUlfBBc-.woff

KFOlCnqEu92Fr1MmWUlfBBc-.woff

512 ms

KFOlCnqEu92Fr1MmYUtfBBc-.woff

KFOlCnqEu92Fr1MmYUtfBBc-.woff

511 ms

KFOkCnqEu92Fr1Mu51xIIzQ.woff

KFOkCnqEu92Fr1Mu51xIIzQ.woff

511 ms

KFOjCnqEu92Fr1Mu51S7ACc6CsI.woff

KFOjCnqEu92Fr1Mu51S7ACc6CsI.woff

579 ms

KFOjCnqEu92Fr1Mu51TjASc6CsI.woff

KFOjCnqEu92Fr1Mu51TjASc6CsI.woff

510 ms

KFOiCnqEu92Fr1Mu51QrEzAdKQ.woff

KFOiCnqEu92Fr1Mu51QrEzAdKQ.woff

509 ms

KFOjCnqEu92Fr1Mu51TzBic6CsI.woff

KFOjCnqEu92Fr1Mu51TzBic6CsI.woff

578 ms

KFOjCnqEu92Fr1Mu51TLBCc6CsI.woff

KFOjCnqEu92Fr1Mu51TLBCc6CsI.woff

578 ms

elementskit.woff

elementskit.woff

943 ms

fa-brands-400.woff

fa-brands-400.woff

666 ms

fa-brands-400.woff

fa-brands-400.woff

619 ms

wpxpress.ttf

wpxpress.ttf

788 ms

collect

collect

143 ms

collect

collect

59 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: