5.3 sec in total
224 ms
4.6 sec
482 ms
Welcome to mage.com homepage info - get ready to check Mage best content for India right away, or after learning these important things about mage.com
Mage Publishes literature books about Persian food, history, poetry and the Shahnameh of Ferdowsi, the culture of Iran, Iranian music, Persian empire, and gardens of Persia.
Visit mage.comWe analyzed Mage.com page load time and found that the first response time was 224 ms and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
mage.com performance score
name
value
score
weighting
Value9.0 s
0/100
10%
Value14.4 s
0/100
25%
Value14.1 s
1/100
10%
Value640 ms
47/100
30%
Value0
100/100
15%
Value16.9 s
5/100
10%
224 ms
190 ms
691 ms
278 ms
277 ms
Our browser made a total of 70 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Mage.com, 83% (58 requests) were made to Magepublishers.com and 3% (2 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Magepublishers.com.
Page size can be reduced by 937.5 kB (50%)
1.9 MB
941.1 kB
In fact, the total size of Mage.com main page is 1.9 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. 65% of websites need less resources to load. Images take 740.4 kB which makes up the majority of the site volume.
Potential reduce by 148.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 148.4 kB or 82% of the original size.
Potential reduce by 20.7 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. Mage images are well optimized though.
Potential reduce by 426.6 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 426.6 kB or 76% of the original size.
Potential reduce by 341.8 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. Mage.com needs all CSS files to be minified and compressed as it can save up to 341.8 kB or 86% of the original size.
Number of requests can be reduced by 39 (62%)
63
24
The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mage. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
mage.com
224 ms
magepublishers.com
190 ms
magepublishers.com
691 ms
custom.css
278 ms
style.css
277 ms
css.minifier.php
1491 ms
style.min.css
425 ms
font-awesome.min.css
167 ms
wp_shopping_cart_style.css
258 ms
theme-style.css
649 ms
jquery.min.js
525 ms
jquery-migrate.min.js
325 ms
js
202 ms
markermanager.js
426 ms
api.js
183 ms
flexslider.css
372 ms
style.css
108 ms
style.css
224 ms
jquery.flexslider.js
218 ms
core.min.js
169 ms
tabs.min.js
225 ms
supreme.js
272 ms
menu.min.js
273 ms
regenerator-runtime.min.js
284 ms
wp-polyfill.min.js
285 ms
dom-ready.min.js
354 ms
hooks.min.js
328 ms
i18n.min.js
353 ms
a11y.min.js
352 ms
autocomplete.min.js
384 ms
tevolution-script.min.js
399 ms
tabber.js
398 ms
bootstrap-mini.js
399 ms
script.js
394 ms
cookie.js
436 ms
modernizr.js
457 ms
jquery.flexslider-min.js
458 ms
jquery.megamenu.1.2.js
458 ms
jquery.hoverIntent.minified.js
458 ms
foundation.min.js
654 ms
style.css
238 ms
css
50 ms
gen_204
75 ms
recaptcha__en.js
65 ms
style.css
937 ms
css
156 ms
sm-facebook.png
519 ms
sm-twitter.png
508 ms
banner_pub_980w_w.gif
90 ms
search.png
1270 ms
aedt_275w.jpg
513 ms
mlpc_370h.jpg
504 ms
ppe_370h.jpg
509 ms
fol_cover_new_370h-165x220.jpg
504 ms
1949445070.MAIN_-165x220.jpg
502 ms
sfot_370h-165x220.jpg
509 ms
fsii_370h-165x220.jpg
507 ms
pts_370h-165x220.jpg
505 ms
LAM_275w-165x220.jpg
508 ms
folb_370h-165x220.jpg
529 ms
abop_cover_370h-165x220.jpg
509 ms
momhb_275w-165x220.jpg
527 ms
wtbdtd_cover_400w-165x220.jpg
527 ms
phn1_hc_370h-165x220.jpg
522 ms
hopi_275w-165x220.jpg
546 ms
nitf_275w-165x220.jpg
561 ms
ipad_montage_1200h.jpg
849 ms
OZpEg_xvsDZQL_LKIF7q4jP3w2j_.ttf
245 ms
OZpEg_xvsDZQL_LKIF7q4jP3w2j_.ttf
417 ms
menu-sub-indicator.png
56 ms
mage.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.
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
Form elements do not have associated labels
mage.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
mage.com SEO score
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mage.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 Mage.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.
mage.com
Open Graph data is detected on the main page of Mage. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: