Tools & Wizards About Us
century.ae screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 53

    Accessibility

    Visual factors better than
    that of 22% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 66

    SEO

    Google-friendlier than
    25% of websites

century.ae

Invest with UAE’s Best Broker | Century Financial

Page Load Speed

5 sec in total

First Response

531 ms

Resources Loaded

3.6 sec

Page Rendered

864 ms

century.ae screenshot

About Website

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

Start investing in Shares, ETFs, Gold, Indices and more with Century Financial, UAE’s SCA-Regulated, Award-Winning Broker. Secure and Reliable Trading Platform & App.

Visit century.ae

Key Findings

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

Performance Metrics

century.ae performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

47/100

10%

LCP (Largest Contentful Paint)

Value14.5 s

0/100

25%

SI (Speed Index)

Value9.9 s

10/100

10%

TBT (Total Blocking Time)

Value1,220 ms

20/100

30%

CLS (Cumulative Layout Shift)

Value0.279

43/100

15%

TTI (Time to Interactive)

Value19.8 s

2/100

10%

Network Requests Diagram

century.ae

531 ms

503 ms

common.css

82 ms

evergage.min.js

37 ms

collect.js

352 ms

Our browser made a total of 78 requests to load all elements on the main page. We found that 28% of them (22 requests) were addressed to the original Century.ae, 45% (35 requests) were made to D10t455z86w23i.cloudfront.net and 9% (7 requests) were made to Upload.century.ae. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source D10t455z86w23i.cloudfront.net.

Page Optimization Overview & Recommendations

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

Content Size

1.7 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Century.ae main page is 1.7 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. Images take 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 132.9 kB

  • Original 155.0 kB
  • After minification 118.0 kB
  • After compression 22.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. This page needs HTML code to be minified as it can gain 37.0 kB, which is 24% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 132.9 kB or 86% of the original size.

Image Optimization

-23%

Potential reduce by 352.5 kB

  • Original 1.5 MB
  • After minification 1.2 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. Obviously, Century needs image optimization as it can save up to 352.5 kB or 23% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-4%

Potential reduce by 921 B

  • Original 23.0 kB
  • After minification 23.0 kB
  • After compression 22.1 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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 121 B

  • Original 26.0 kB
  • After minification 26.0 kB
  • After compression 25.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. Century.ae has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 23 (34%)

Requests Now

68

After Optimization

45

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

century.ae

century.ae

531 ms

503 ms

common.css

common.css

82 ms

evergage.min.js

evergage.min.js

37 ms

collect.js

collect.js

352 ms

index.css

index.css

160 ms

company_logo_2022__1697520422.png

company_logo_2022__1697520422.png

33 ms

icomoon.css

icomoon.css

227 ms

loader-small.gif

loader-small.gif

345 ms

ar.png

ar.png

415 ms

no-1-3.png

no-1-3.png

520 ms

man-3.png

man-3.png

586 ms

Awards-2023.png

Awards-2023.png

519 ms

man-sitting-and-enjoying-somthing-rev.png

man-sitting-and-enjoying-somthing-rev.png

629 ms

jquery.min.js

jquery.min.js

64 ms

jquery-ui.min.js

jquery-ui.min.js

95 ms

tabs.min.css

tabs.min.css

82 ms

jquery-migrate.min.js

jquery-migrate.min.js

84 ms

wow.min.js

wow.min.js

41 ms

magnific-popup.min.css

magnific-popup.min.css

53 ms

slick.js

slick.js

344 ms

language.plugin.js

language.plugin.js

344 ms

OneSignalSDK.js

OneSignalSDK.js

45 ms

common.js

common.js

345 ms

parallax.js

parallax.js

346 ms

700.png

700.png

1534 ms

whatapp.svg

whatapp.svg

170 ms

icon-search.svg

icon-search.svg

172 ms

sprite-index.png

sprite-index.png

235 ms

dotted-map.png

dotted-map.png

236 ms

partnership-bg.jpg

partnership-bg.jpg

341 ms

footerlogo.png

footerlogo.png

173 ms

35-Years.png

35-Years.png

907 ms

24-Hours.png

24-Hours.png

908 ms

License.png

License.png

908 ms

Research.png

Research.png

909 ms

lady.png

lady.png

523 ms

wire.png

wire.png

762 ms

Graph-banner.png

Graph-banner.png

675 ms

Man-banner.png

Man-banner.png

868 ms

Phone-banner.png

Phone-banner.png

908 ms

sounding-board-image-min.jpg

sounding-board-image-min.jpg

878 ms

Background.png

Background.png

1019 ms

Icon-1.png

Icon-1.png

677 ms

Icon-2.png

Icon-2.png

1016 ms

Icon-3.png

Icon-3.png

1099 ms

Icon-4.png

Icon-4.png

873 ms

Icon-5.png

Icon-5.png

877 ms

Icon-6.png

Icon-6.png

1228 ms

Icon-7.png

Icon-7.png

882 ms

Icon-8.png

Icon-8.png

1221 ms

App-Store.png

App-Store.png

911 ms

button.png

button.png

1262 ms

Google-Play2.png

Google-Play2.png

1019 ms

Web-Platform.png

Web-Platform.png

1027 ms

our-edge-img.png

our-edge-img.png

1551 ms

award-img-min.jpg

award-img-min.jpg

1402 ms

Most-innovative-trading-technology-2024.png

Most-innovative-trading-technology-2024.png

1441 ms

Award1.png

Award1.png

1225 ms

Award2.png

Award2.png

1572 ms

Award3.png

Award3.png

1563 ms

Award4.png

Award4.png

1618 ms

Award6.png

Award6.png

1408 ms

English-Footer.png

English-Footer.png

1831 ms

live-icon2.png

live-icon2.png

1442 ms

x.svg

x.svg

841 ms

808.svg

808.svg

996 ms

ProximaNova-Regular.woff

ProximaNova-Regular.woff

167 ms

ProximaNova-Light.woff

ProximaNova-Light.woff

270 ms

ProximaNova-Semibold.woff

ProximaNova-Semibold.woff

240 ms

ProximaNova-Bold.woff

ProximaNova-Bold.woff

168 ms

icomoon.ttf

icomoon.ttf

167 ms

icomoon.ttf

icomoon.ttf

239 ms

gtm.js

gtm.js

176 ms

fbevents.js

fbevents.js

174 ms

dtm.js

dtm.js

679 ms

insight.min.js

insight.min.js

171 ms

insight_tag_errors.gif

insight_tag_errors.gif

100 ms

Accessibility Review

century.ae accessibility score

53

Accessibility Issues

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-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[aria-*] attributes do not have valid values

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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.

Best Practices

century.ae best practices score

67

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

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

century.ae SEO score

66

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

High

Image elements do not have [alt] attributes

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 doesn't use 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 Century.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 Century.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

century.ae

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