4.3 sec in total
161 ms
3.6 sec
453 ms
Click here to check amazing Eko Atlantic content for Nigeria. Otherwise, check out these important facts you probably never knew about ekoatlantic.com
WELCOME TO EKO ATLANTIC INVEST IN THE FUTURE OF LAGOS LAND Explore RESIDENTIAL Explore COMMERCIAL Explore FREE-ZONE Explore RETAIL Explore
Visit ekoatlantic.comWe analyzed Ekoatlantic.com page load time and found that the first response time was 161 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
ekoatlantic.com performance score
name
value
score
weighting
Value4.0 s
23/100
10%
Value12.4 s
0/100
25%
Value11.4 s
5/100
10%
Value1,100 ms
23/100
30%
Value0.011
100/100
15%
Value28.5 s
0/100
10%
161 ms
2095 ms
15 ms
72 ms
22 ms
Our browser made a total of 112 requests to load all elements on the main page. We found that 57% of them (64 requests) were addressed to the original Ekoatlantic.com, 15% (17 requests) were made to Fonts.gstatic.com and 6% (7 requests) were made to App.roho.ai. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Ekoatlantic.com.
Page size can be reduced by 2.4 MB (38%)
6.3 MB
3.9 MB
In fact, the total size of Ekoatlantic.com main page is 6.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. Only a small number of websites need less resources to load. Images take 3.7 MB which makes up the majority of the site volume.
Potential reduce by 279.4 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 279.4 kB or 85% of the original size.
Potential reduce by 2.0 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, Eko Atlantic needs image optimization as it can save up to 2.0 MB or 53% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 2.0 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.
Potential reduce by 149.5 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. Ekoatlantic.com needs all CSS files to be minified and compressed as it can save up to 149.5 kB or 36% of the original size.
Number of requests can be reduced by 74 (88%)
84
10
The browser has sent 84 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Eko Atlantic. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 60 to 1 for CSS and as a result speed up the page load time.
ekoatlantic.com
161 ms
www.ekoatlantic.com
2095 ms
bootstrap-light.min.css
15 ms
base.min.css
72 ms
woo-widget-price-filter.min.css
22 ms
dashicons.min.css
22 ms
common-style.css
21 ms
slick.min.css
77 ms
font-awesome.min.css
26 ms
style-blocks-htmega.css
155 ms
lc-public.css
31 ms
sticky-social-icons-public.css
24 ms
htbbootstrap.css
28 ms
animation.css
32 ms
htmega-keyframes.css
35 ms
custom-frontend-lite.min.css
36 ms
swiper.min.css
34 ms
post-13.css
41 ms
custom-pro-frontend-lite.min.css
41 ms
post-15602.css
86 ms
post-19418.css
132 ms
post-18659.css
42 ms
post-17276.css
43 ms
post-17081.css
91 ms
post-17086.css
69 ms
post-15789.css
73 ms
all.css
76 ms
widget-wd-recent-posts.min.css
75 ms
widget-nav.min.css
81 ms
wp-gutenberg.min.css
81 ms
int-elem-base.min.css
83 ms
int-elementor-pro.min.css
82 ms
mod-animations-keyframes.min.css
85 ms
opt-widget-collapse.min.css
86 ms
el-text-block.min.css
89 ms
opt-scrolltotop.min.css
88 ms
header-el-fullscreen-menu.min.css
87 ms
css
47 ms
css
67 ms
opt-cookies.min.css
86 ms
v4-shims.css
85 ms
font-awesome.min.css
76 ms
custom-pro-widget-call-to-action.min.css
78 ms
custom-widget-icon-list.min.css
79 ms
widget-carousel.min.css
73 ms
custom-pro-widget-nav-menu.min.css
73 ms
htmega-widgets.css
326 ms
post-17261.css
116 ms
post-17264.css
114 ms
post-17265.css
105 ms
post-17269.css
317 ms
post-17105.css
102 ms
post-17826.css
103 ms
post-17827.css
106 ms
post-17828.css
108 ms
animations.min.css
106 ms
smush-lazy-load.min.js
82 ms
1698242400965x369112387113451500
854 ms
DJI_0076.jpg
114 ms
14.jpg
109 ms
TM-3.jpg
563 ms
PHOENIX-View-C.jpg
113 ms
PP_BOARD-05-1.jpg
560 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf
501 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf
502 ms
AvenirLTStd-Black.woff
444 ms
AvenirLTStd-Roman.woff
445 ms
AvenirLTStd-Book.woff
445 ms
fa-brands-400.ttf
61 ms
Logo.png
58 ms
MTU4Mjc0Nw==
39 ms
early.js
53 ms
run.css
87 ms
pre_run_jquery.js
57 ms
run.js
163 ms
static.js
160 ms
dynamic.js
100 ms
download.js
123 ms
feather-icons
163 ms
icons.js
145 ms
scrollreveal
128 ms
aos-2.3.4.css
139 ms
aos-2.3.4.js
144 ms
index.js
182 ms
TxtAnime.js
212 ms
main.css
27 ms
bundle.js
96 ms
css
74 ms
style.css
162 ms
style.css
137 ms
scrollreveal@4.0.9
32 ms
scrollreveal.js
17 ms
sdk.js
47 ms
d6lIkaiiRdih4SpP_SQvyQ.ttf
5 ms
NGSnv5HMAFg6IuGlBNMjxJEL2VmU3NS7Z2mjDw-aWy5X.ttf
9 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuLyfAZ9hjQ.ttf
18 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuI6fAZ9hjQ.ttf
15 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuGKYAZ9hjQ.ttf
19 ms
UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuFuYAZ9hjQ.ttf
19 ms
0nksC9P7MfYHj2oFtYm2ChTtgP4.ttf
18 ms
pxiByp8kv8JHgFVrLDz8Z1xlEA.ttf
13 ms
pxiEyp8kv8JHgFVrJJfedw.ttf
19 ms
pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf
42 ms
pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf
42 ms
pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf
43 ms
ijwGs572Xtc6ZYQws9YVwllKVG8qX1oyOymuFpmJxAct.ttf
42 ms
ijwGs572Xtc6ZYQws9YVwllKVG8qX1oyOymuJJmJxAct.ttf
43 ms
4iCv6KVjbNBYlgoCxCvjsGyI.ttf
43 ms
Inter-UI-Black.ttf
51 ms
Inter-UI-SemiBold.ttf
44 ms
sdk.js
11 ms
28 ms
ekoatlantic.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
ekoatlantic.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
ekoatlantic.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ekoatlantic.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 Ekoatlantic.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.
ekoatlantic.com
Open Graph data is detected on the main page of Eko Atlantic. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: