1.2 sec in total
175 ms
799 ms
275 ms
Welcome to mapeditor.org homepage info - get ready to check Map Editor best content for United States right away, or after learning these important things about mapeditor.org
Flexible level editor
Visit mapeditor.orgWe analyzed Mapeditor.org page load time and found that the first response time was 175 ms and then it took 1.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.
mapeditor.org performance score
name
value
score
weighting
Value2.2 s
79/100
10%
Value4.7 s
32/100
25%
Value2.2 s
99/100
10%
Value0 ms
100/100
30%
Value0.001
100/100
15%
Value2.2 s
99/100
10%
175 ms
119 ms
69 ms
62 ms
77 ms
Our browser made a total of 41 requests to load all elements on the main page. We found that 83% of them (34 requests) were addressed to the original Mapeditor.org, 5% (2 requests) were made to Cdn.transifex.com and 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (306 ms) relates to the external source Cdn.transifex.com.
Page size can be reduced by 210.7 kB (18%)
1.2 MB
957.6 kB
In fact, the total size of Mapeditor.org main page is 1.2 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. 40% of websites need less resources to load. Images take 930.4 kB which makes up the majority of the site volume.
Potential reduce by 23.8 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 3.3 kB, which is 11% 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 23.8 kB or 82% of the original size.
Potential reduce by 47.1 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. Map Editor images are well optimized though.
Potential reduce by 32.4 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 32.4 kB or 41% of the original size.
Potential reduce by 107.4 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. Mapeditor.org needs all CSS files to be minified and compressed as it can save up to 107.4 kB or 82% of the original size.
Number of requests can be reduced by 10 (26%)
38
28
The browser has sent 38 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Map Editor. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
mapeditor.org
175 ms
www.mapeditor.org
119 ms
bootstrap.min.css
69 ms
bootstrap-theme.min.css
62 ms
fontawesome.css
77 ms
jquery.fancybox.css
58 ms
index.css
64 ms
live.js
141 ms
jquery-1.9.1.min.js
7 ms
bootstrap.min.js
73 ms
jquery.fancybox.pack.js
87 ms
base.css
39 ms
tile40.png
75 ms
analytics.js
48 ms
patreon.mapeditor.org
223 ms
settings.all.jsonp
306 ms
tile98.png
46 ms
tile104.png
46 ms
tile68.png
43 ms
tile70.png
44 ms
tile66.png
45 ms
tile100.png
44 ms
tile102.png
82 ms
tile106.png
77 ms
tile74.png
82 ms
tile38.png
78 ms
tile34.png
79 ms
tile72.png
82 ms
tile36.png
111 ms
tree.png
109 ms
tiled-logo-white.png
150 ms
screenshot-terrain-thumb.png
155 ms
screenshot-objects-thumb.png
200 ms
screenshot-isometric-thumb.png
211 ms
banner_loomsdk.png
192 ms
banner_egret.png
250 ms
banner_atomic.png
193 ms
grid.png
194 ms
fontawesome-webfont.woff
241 ms
collect
12 ms
collect
61 ms
mapeditor.org 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
Image elements do not have [alt] attributes
Links do not have a discernible name
mapeditor.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
mapeditor.org SEO score
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
Tap targets are not sized appropriately
EN
EN
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mapeditor.org 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 Mapeditor.org main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
mapeditor.org
Open Graph description is not detected on the main page of Map Editor. 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: