Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 57% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 88

    SEO

    Google-friendlier than
    66% of websites

communicate.ae

Home - Communicate Online | Activate the digital transformation reshaping the GCC advertising & marketing industry

Page Load Speed

3.6 sec in total

First Response

59 ms

Resources Loaded

3 sec

Page Rendered

552 ms

communicate.ae screenshot

About Website

Click here to check amazing Communicate content for United Arab Emirates. Otherwise, check out these important facts you probably never knew about communicate.ae

Communicate is a multi-format, engaging platform on a mission: to help our stakeholders understand and activate the digital transformation reshaping the advertising & marketing industry in the GCC and...

Visit communicate.ae

Key Findings

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

Performance Metrics

communicate.ae performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

56/100

10%

LCP (Largest Contentful Paint)

Value20.0 s

0/100

25%

SI (Speed Index)

Value10.1 s

9/100

10%

TBT (Total Blocking Time)

Value3,320 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.125

83/100

15%

TTI (Time to Interactive)

Value22.1 s

1/100

10%

Network Requests Diagram

communicateonline.me

59 ms

style.css

30 ms

jquery.jscrollpane.css

49 ms

ie8.css

34 ms

flexslider.css

34 ms

Our browser made a total of 305 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Communicate.ae, 7% (20 requests) were made to Static.xx.fbcdn.net and 5% (14 requests) were made to Images.intellitxt.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Communicateonline.me.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.8 MB (16%)

Content Size

11.1 MB

After Optimization

9.3 MB

In fact, the total size of Communicate.ae main page is 11.1 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. 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 9.2 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 520.0 kB

  • Original 664.6 kB
  • After minification 640.8 kB
  • After compression 144.6 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 520.0 kB or 78% of the original size.

Image Optimization

-4%

Potential reduce by 398.8 kB

  • Original 9.2 MB
  • After minification 8.8 MB

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. Communicate images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 739.9 kB

  • Original 1.1 MB
  • After minification 1.0 MB
  • After compression 314.9 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 739.9 kB or 70% of the original size.

CSS Optimization

-82%

Potential reduce by 119.5 kB

  • Original 145.7 kB
  • After minification 144.0 kB
  • After compression 26.2 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. Communicate.ae needs all CSS files to be minified and compressed as it can save up to 119.5 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 138 (46%)

Requests Now

302

After Optimization

164

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

Accessibility Review

communicate.ae accessibility score

84

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.

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

communicate.ae best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

communicate.ae SEO score

88

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

Image elements do not have [alt] attributes

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 Communicate.ae 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 Communicate.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

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