Tools & Wizards About Us
fortune5.com screenshot

Report Summary

  • 27

    Performance

    Renders faster than
    46% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

fortune5.com

Fortune 5 Developments | Dubai

Page Load Speed

7.2 sec in total

First Response

500 ms

Resources Loaded

6.5 sec

Page Rendered

156 ms

fortune5.com screenshot

About Website

Visit fortune5.com now to see the best up-to-date Fortune 5 content for United Arab Emirates and also check out these interesting facts you probably never knew about fortune5.com

Fortune 5 Developments is a well-recognized established brand specializing in real estate investment and asset management in Dubai.

Visit fortune5.com

Key Findings

We analyzed Fortune5.com page load time and found that the first response time was 500 ms and then it took 6.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

fortune5.com performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.6 s

5/100

10%

LCP (Largest Contentful Paint)

Value6.7 s

7/100

25%

SI (Speed Index)

Value12.1 s

3/100

10%

TBT (Total Blocking Time)

Value940 ms

29/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value16.1 s

6/100

10%

Network Requests Diagram

fortune5.com

500 ms

fortune5.com

1194 ms

premium-addons.min.css

468 ms

styles.css

688 ms

intlTelInput.min.css

685 ms

Our browser made a total of 106 requests to load all elements on the main page. We found that 75% of them (80 requests) were addressed to the original Fortune5.com, 12% (13 requests) were made to Fonts.gstatic.com and 5% (5 requests) were made to Gstatic.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Fortune5.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 230.1 kB (13%)

Content Size

1.8 MB

After Optimization

1.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fortune5.com main page is 1.8 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. 70% of websites need less resources to load. Images take 776.5 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 88.5 kB

  • Original 114.5 kB
  • After minification 113.1 kB
  • After compression 26.0 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 88.5 kB or 77% of the original size.

Image Optimization

-0%

Potential reduce by 543 B

  • Original 776.5 kB
  • After minification 776.0 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. Fortune 5 images are well optimized though.

JavaScript Optimization

-10%

Potential reduce by 63.5 kB

  • Original 646.6 kB
  • After minification 646.6 kB
  • After compression 583.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

-27%

Potential reduce by 77.5 kB

  • Original 287.5 kB
  • After minification 287.5 kB
  • After compression 210.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. Fortune5.com needs all CSS files to be minified and compressed as it can save up to 77.5 kB or 27% of the original size.

Requests Breakdown

Number of requests can be reduced by 78 (87%)

Requests Now

90

After Optimization

12

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fortune5.com

fortune5.com

500 ms

fortune5.com

fortune5.com

1194 ms

premium-addons.min.css

premium-addons.min.css

468 ms

styles.css

styles.css

688 ms

intlTelInput.min.css

intlTelInput.min.css

685 ms

countrySelect.min.css

countrySelect.min.css

689 ms

rs6.css

rs6.css

928 ms

wpsm-style.css

wpsm-style.css

698 ms

bootstrap.min.css

bootstrap.min.css

701 ms

bootstrap-select.min.css

bootstrap-select.min.css

912 ms

all.min.css

all.min.css

1143 ms

icons.css

icons.css

917 ms

slick-min.css

slick-min.css

930 ms

slick-theme-min.css

slick-theme-min.css

934 ms

jquery-ui.min.css

jquery-ui.min.css

1140 ms

radio-checkbox-min.css

radio-checkbox-min.css

1146 ms

bootstrap-datepicker.min.css

bootstrap-datepicker.min.css

1159 ms

main.css

main.css

1627 ms

styling-options.css

styling-options.css

1166 ms

style.css

style.css

1368 ms

elementor-icons.min.css

elementor-icons.min.css

1369 ms

frontend.min.css

frontend.min.css

1604 ms

swiper.min.css

swiper.min.css

1390 ms

post-17348.css

post-17348.css

1398 ms

frontend.min.css

frontend.min.css

1826 ms

post-10.css

post-10.css

1596 ms

general.min.css

general.min.css

1624 ms

ecs-style.css

ecs-style.css

1634 ms

css

css

43 ms

jquery.min.js

jquery.min.js

2053 ms

jquery-migrate.min.js

jquery-migrate.min.js

1849 ms

rbtools.min.js

rbtools.min.js

1858 ms

rs6.min.js

rs6.min.js

2321 ms

ecs_ajax_pagination.js

ecs_ajax_pagination.js

1861 ms

ecs.js

ecs.js

2076 ms

js

js

64 ms

index.js

index.js

2076 ms

index.js

index.js

2090 ms

codedropz-uploader-min.js

codedropz-uploader-min.js

2094 ms

api.js

api.js

74 ms

intlTelInput.min.js

intlTelInput.min.js

2279 ms

css

css

20 ms

countrySelect.min.js

countrySelect.min.js

1807 ms

page-scroll-to-id.min.js

page-scroll-to-id.min.js

1614 ms

wpsm-script.js

wpsm-script.js

1710 ms

bootstrap.bundle.min.js

bootstrap.bundle.min.js

1707 ms

bootstrap-select.min.js

bootstrap-select.min.js

1820 ms

modernizr.custom.js

modernizr.custom.js

1810 ms

slideout.min.js

slideout.min.js

1777 ms

lightbox.min.js

lightbox.min.js

1775 ms

theia-sticky-sidebar.min.js

theia-sticky-sidebar.min.js

1764 ms

slick.min.js

slick.min.js

1763 ms

core.min.js

core.min.js

1811 ms

menu.min.js

menu.min.js

1603 ms

dom-ready.min.js

dom-ready.min.js

1612 ms

hooks.min.js

hooks.min.js

1645 ms

i18n.min.js

i18n.min.js

1634 ms

a11y.min.js

a11y.min.js

1634 ms

autocomplete.min.js

autocomplete.min.js

1604 ms

mouse.min.js

mouse.min.js

1601 ms

slider.min.js

slider.min.js

1593 ms

custom.js

custom.js

1624 ms

wp-polyfill.min.js

wp-polyfill.min.js

1429 ms

index.js

index.js

1420 ms

general.min.js

general.min.js

1565 ms

make-column-clickable.js

make-column-clickable.js

1569 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

1579 ms

webpack.runtime.min.js

webpack.runtime.min.js

1406 ms

frontend-modules.min.js

frontend-modules.min.js

1409 ms

frontend.min.js

frontend.min.js

1403 ms

waypoints.min.js

waypoints.min.js

1566 ms

frontend.min.js

frontend.min.js

1351 ms

elements-handlers.min.js

elements-handlers.min.js

1367 ms

underscore.min.js

underscore.min.js

1409 ms

wp-util.min.js

wp-util.min.js

1399 ms

frontend.min.js

frontend.min.js

1400 ms

f5_logo.svg

f5_logo.svg

1324 ms

Home-page_txt.jpg

Home-page_txt.jpg

2464 ms

FBox_w.svg

FBox_w.svg

1304 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrQ.ttf

18 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaorCIPrQ.ttf

34 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao7CIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao7CIPrQ.ttf

46 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf

50 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCIPrQ.ttf

51 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCIPrQ.ttf

255 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrQ.ttf

49 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCIPrQ.ttf

50 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCIPrQ.ttf

71 ms

S6uyw4BMUTPHjx4wWw.ttf

S6uyw4BMUTPHjx4wWw.ttf

70 ms

houzez-iconfont.ttf

houzez-iconfont.ttf

1291 ms

recaptcha__en.js

recaptcha__en.js

28 ms

anchor

anchor

46 ms

386 ms

prev.png

prev.png

234 ms

next.png

next.png

357 ms

loading.gif

loading.gif

375 ms

close.png

close.png

424 ms

styles__ltr.css

styles__ltr.css

8 ms

recaptcha__en.js

recaptcha__en.js

21 ms

8AXZAK1i6BpqK69J99oN0p3RtJQ1PGMK6D_RgjsU7ps.js

8AXZAK1i6BpqK69J99oN0p3RtJQ1PGMK6D_RgjsU7ps.js

36 ms

webworker.js

webworker.js

34 ms

logo_48.png

logo_48.png

23 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

34 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

8 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

34 ms

recaptcha__en.js

recaptcha__en.js

35 ms

Accessibility Review

fortune5.com accessibility score

84

Accessibility Issues

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

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.

Best Practices

fortune5.com best practices score

92

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

Page has valid source maps

SEO Factors

fortune5.com SEO score

93

Search Engine Optimization Advices

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 Fortune5.com 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 Fortune5.com 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

fortune5.com

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