3.2 sec in total
531 ms
2.5 sec
151 ms
Welcome to m.ea.de homepage info - get ready to check M EA best content for Austria right away, or after learning these important things about m.ea.de
Electronic Arts ist ein führender Publisher von Spielen für Konsolen, PC und Mobilgeräte.
Visit m.ea.deWe analyzed M.ea.de page load time and found that the first response time was 531 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
m.ea.de performance score
name
value
score
weighting
Value4.0 s
22/100
10%
Value23.0 s
0/100
25%
Value12.2 s
3/100
10%
Value8,300 ms
0/100
30%
Value1.237
1/100
15%
Value17.8 s
4/100
10%
531 ms
190 ms
303 ms
220 ms
805 ms
Our browser made a total of 30 requests to load all elements on the main page. We found that 87% of them (26 requests) were addressed to the original M.ea.de, 7% (2 requests) were made to Google-analytics.com and 7% (2 requests) were made to Banner.electronic-arts.de. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain M.ea.de.
Page size can be reduced by 444.4 kB (51%)
874.3 kB
429.9 kB
In fact, the total size of M.ea.de main page is 874.3 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 20% of websites need less resources to load. Javascripts take 352.7 kB which makes up the majority of the site volume.
Potential reduce by 11.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. This page needs HTML code to be minified as it can gain 1.8 kB, which is 12% 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 11.4 kB or 78% of the original size.
Potential reduce by 811 B
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. M EA images are well optimized though.
Potential reduce by 238.7 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 238.7 kB or 68% of the original size.
Potential reduce by 193.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. M.ea.de needs all CSS files to be minified and compressed as it can save up to 193.5 kB or 88% of the original size.
We found no issues to fix!
29
29
The browser has sent 29 CSS, Javascripts, AJAX and image requests in order to completely render the main page of M EA. According to our analytics all requests are already optimized.
m.ea.de
531 ms
fonts.css
190 ms
framework7.min.css
303 ms
my-app.min.css
220 ms
ea2go.pack.min.js
805 ms
ga.js
44 ms
lg.php
350 ms
ea-logo.svg
191 ms
icon-ea-logo-small.jpg
193 ms
icon-home.svg
615 ms
icon-games.svg
613 ms
icon-news.svg
663 ms
icon-media.svg
759 ms
icon-support.svg
779 ms
lg.php
337 ms
source-sans-pro-v9-latin-300.woff
873 ms
source-sans-pro-v9-latin-200.woff
864 ms
source-sans-pro-v9-latin-regular.woff
904 ms
5239e8293617b0e4148dc9cbfd7b3317.max656x656.jpg
923 ms
b91b463a5e1408e0347ec2abc1b1c36b.max547x547.jpg
928 ms
6aae33a01800288dd18e1d2a91cdb00d.max547x547.jpg
1039 ms
37588835569631cc2c582b700a81edfb.max547x547.jpg
722 ms
d70dbc5311d1bbfb5867dd07898e55c2.max547x547.jpg
834 ms
f6463a3a5c553f71562c5d8a45de73f4.max547x547.jpg
911 ms
625a5a523ab14a754b7b32f7f70de122.max547x547.jpg
991 ms
fed6568c9655edb3563f22b7c7a7b471.max547x547.jpg
896 ms
__utm.gif
15 ms
46be0db2ff30e900b987994445fcb9b8.max547x547.jpg
935 ms
5b35f5c1ec10e2c972f1603f806b3f74.max547x547.jpg
1045 ms
3ec3ddea3b18f1097c73731d63b06900.max547x547.jpg
1017 ms
m.ea.de 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-*] attributes do not match their roles
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[role]s are not contained by their required parent element
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
[id] attributes on active, focusable elements are not unique
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
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
m.ea.de 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
Page has valid source maps
m.ea.de SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
DE
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise M.ea.de can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that M.ea.de 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.
m.ea.de
Open Graph description is not detected on the main page of M EA. 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: