3.6 sec in total
205 ms
2.3 sec
1.1 sec
Click here to check amazing Elyland content for Ukraine. Otherwise, check out these important facts you probably never knew about elyland.net
something
Visit elyland.netWe analyzed Elyland.net page load time and found that the first response time was 205 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
elyland.net performance score
name
value
score
weighting
Value4.4 s
16/100
10%
Value8.4 s
2/100
25%
Value4.8 s
68/100
10%
Value140 ms
96/100
30%
Value0.1
89/100
15%
Value6.4 s
59/100
10%
205 ms
507 ms
195 ms
287 ms
478 ms
Our browser made a total of 53 requests to load all elements on the main page. We found that 79% of them (42 requests) were addressed to the original Elyland.net, 9% (5 requests) were made to Fonts.gstatic.com and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Elyland.net.
Page size can be reduced by 209.5 kB (4%)
5.4 MB
5.2 MB
In fact, the total size of Elyland.net main page is 5.4 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. 45% of websites need less resources to load. Images take 5.2 MB which makes up the majority of the site volume.
Potential reduce by 25.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. This page needs HTML code to be minified as it can gain 6.5 kB, which is 20% 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 25.7 kB or 77% of the original size.
Potential reduce by 132.4 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. Elyland images are well optimized though.
Potential reduce by 40.2 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 40.2 kB or 33% of the original size.
Potential reduce by 11.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. Elyland.net needs all CSS files to be minified and compressed as it can save up to 11.2 kB or 25% of the original size.
Number of requests can be reduced by 12 (26%)
46
34
The browser has sent 46 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Elyland. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
elyland.net
205 ms
elyland.net
507 ms
slick.css
195 ms
slick-theme.css
287 ms
elyland.css
478 ms
lightbox.min.css
292 ms
quill.core.css
201 ms
jquery.min.js
25 ms
jquery.mobile.custom.min.js
290 ms
bootstrap.min.js
386 ms
slick.min.js
291 ms
elyland.js
381 ms
lightbox.min.js
386 ms
css
32 ms
analytics.js
156 ms
pattern-bg.jpg
202 ms
close.png
180 ms
loading.gif
181 ms
prev.png
181 ms
next.png
181 ms
arrow-top.png
179 ms
elyland-logo_wh.png
269 ms
draconiusgo-icon.png
366 ms
wormax-icon.png
460 ms
mylands-icon.png
463 ms
wormax2-icon.png
463 ms
mouse-icon.png
271 ms
draconiusgo-bg.jpg
556 ms
draconiusgo_logo-md.png
562 ms
wormax_bg.jpg
562 ms
wormax_logo-md.png
556 ms
mylands-bg.jpg
655 ms
mylands_logo-md.png
656 ms
wormax2_bg.jpg
1037 ms
wormax2_logo-md.png
652 ms
arrow.png
657 ms
news-teaser-Elyland-cancels-token-sales.png
850 ms
news-teaser-clash-and-go-went-live.png
755 ms
news-teaser-two-new-projects-coming%20-in-the-next-couple-of%20months.png
764 ms
team.jpg
1142 ms
workspace.jpg
759 ms
letter-icon.png
851 ms
paperclip.png
856 ms
facebook-logo.png
861 ms
linkedin_logo-white.png
948 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4kaVc.ttf
74 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4kaVc.ttf
75 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4kaVc.ttf
91 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4kaVc.ttf
92 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4kaVc.ttf
92 ms
ajax-loader.gif
819 ms
collect
28 ms
js
65 ms
elyland.net accessibility score
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
[aria-hidden="true"] elements contain focusable descendents
ARIA IDs are not unique
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Image elements do not have [alt] attributes
Form elements do not have associated labels
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
elyland.net best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
elyland.net SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
![]()
EN
![]()
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Elyland.net 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 Elyland.net 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.
elyland.net
Open Graph data is detected on the main page of Elyland. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: