Tools & Wizards About Us
dsp.ae screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

dsp.ae

Healthcare and Life Sciences Hub | Dubai Science Park

Page Load Speed

7.1 sec in total

First Response

1.5 sec

Resources Loaded

5 sec

Page Rendered

581 ms

dsp.ae screenshot

About Website

Visit dsp.ae now to see the best up-to-date Dsp content for United Arab Emirates and also check out these interesting facts you probably never knew about dsp.ae

Dubai Science Park, region's leading free zone for healthcare and life science businesses. Discover medical Centre for lease in this vibrant science campus.

Visit dsp.ae

Key Findings

We analyzed Dsp.ae page load time and found that the first response time was 1.5 sec and then it took 5.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

dsp.ae performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.8 s

4/100

10%

LCP (Largest Contentful Paint)

Value15.4 s

0/100

25%

SI (Speed Index)

Value13.9 s

1/100

10%

TBT (Total Blocking Time)

Value2,150 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value20.9 s

2/100

10%

Network Requests Diagram

dsp.ae

1462 ms

optimized-min.css

40 ms

optimized-min.css

50 ms

optimized-min.css

66 ms

optimized-min.css

91 ms

Our browser made a total of 39 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Dsp.ae, 82% (32 requests) were made to Cdn-tecom.azureedge.net and 8% (3 requests) were made to Policy.cookiereports.com. The less responsive or slowest element that took the longest time to load (2.9 sec) relates to the external source Cdn-tecom.azureedge.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 520.4 kB (35%)

Content Size

1.5 MB

After Optimization

970.3 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Dsp.ae main page is 1.5 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. 75% 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. Javascripts take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 75.3 kB

  • Original 93.0 kB
  • After minification 93.0 kB
  • After compression 17.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 75.3 kB or 81% of the original size.

JavaScript Optimization

-17%

Potential reduce by 188.7 kB

  • Original 1.1 MB
  • After minification 1.1 MB
  • After compression 908.5 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 188.7 kB or 17% of the original size.

CSS Optimization

-85%

Potential reduce by 256.4 kB

  • Original 300.5 kB
  • After minification 57.3 kB
  • After compression 44.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. Dsp.ae needs all CSS files to be minified and compressed as it can save up to 256.4 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 12 (55%)

Requests Now

22

After Optimization

10

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

dsp.ae

dsp.ae

1462 ms

optimized-min.css

optimized-min.css

40 ms

optimized-min.css

optimized-min.css

50 ms

optimized-min.css

optimized-min.css

66 ms

optimized-min.css

optimized-min.css

91 ms

fonts.css

fonts.css

71 ms

api.js

api.js

39 ms

5c6d5f26_panel-en-gb.js

5c6d5f26_panel-en-gb.js

78 ms

optimized-min.js

optimized-min.js

209 ms

optimized-min.js

optimized-min.js

208 ms

optimized-min.js

optimized-min.js

69 ms

optimized-min.js

optimized-min.js

455 ms

gtm.js

gtm.js

427 ms

recaptcha__en.js

recaptcha__en.js

425 ms

jquery.min.js

jquery.min.js

362 ms

in5-logo-white.svg

in5-logo-white.svg

374 ms

in-5-logo-dark.svg

in-5-logo-dark.svg

373 ms

axs-logo-white.svg

axs-logo-white.svg

376 ms

axs-logo-dark.svg

axs-logo-dark.svg

377 ms

DSP_desktop_white.svg

DSP_desktop_white.svg

373 ms

DSP_desktop_dark.svg

DSP_desktop_dark.svg

375 ms

SFCompactText-Light.woff

SFCompactText-Light.woff

1241 ms

SFCompactText-Light.woff

SFCompactText-Light.woff

377 ms

SFCompactText-Regular.woff

SFCompactText-Regular.woff

1225 ms

SFCompactText-Regular.woff

SFCompactText-Regular.woff

375 ms

icon-loading.gif

icon-loading.gif

731 ms

SFProDisplay-Bold.woff

SFProDisplay-Bold.woff

114 ms

SFProDisplay-Bold.woff

SFProDisplay-Bold.woff

114 ms

SFProDisplay-Black.woff

SFProDisplay-Black.woff

114 ms

SFProDisplay-Black.woff

SFProDisplay-Black.woff

115 ms

SFProDisplay-Semibold.woff

SFProDisplay-Semibold.woff

2882 ms

SFProDisplay-Semibold.woff

SFProDisplay-Semibold.woff

1014 ms

SFProDisplay-Regular.woff

SFProDisplay-Regular.woff

166 ms

SFProDisplay-Regular.woff

SFProDisplay-Regular.woff

167 ms

SFProDisplay-Light.woff

SFProDisplay-Light.woff

166 ms

SFProDisplay-Light.woff

SFProDisplay-Light.woff

167 ms

TecomIcon-woff.woff

TecomIcon-woff.woff

167 ms

TecomIcon-woff.woff

TecomIcon-woff.woff

643 ms

120 ms

Accessibility Review

dsp.ae accessibility score

89

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.

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 IDs are not unique

Best Practices

dsp.ae best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

dsp.ae SEO score

100

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dsp.ae can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Dsp.ae 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

dsp.ae

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