11.8 sec in total
2.2 sec
9.2 sec
454 ms
Visit magozine.it now to see the best up-to-date Mago Zine content and also check out these interesting facts you probably never knew about magozine.it
Blog di controinformazione con articoli ed editoriali dai movimenti, su questioni sociali, lavoro, emergenza climatica e politica assembleare dal basso. Approfondimenti di controcultura con recensioni...
Visit magozine.itWe analyzed Magozine.it page load time and found that the first response time was 2.2 sec and then it took 9.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
magozine.it performance score
name
value
score
weighting
Value4.9 s
10/100
10%
Value5.1 s
26/100
25%
Value6.9 s
33/100
10%
Value70 ms
99/100
30%
Value0.001
100/100
15%
Value5.8 s
67/100
10%
2175 ms
21 ms
511 ms
26 ms
1395 ms
Our browser made a total of 112 requests to load all elements on the main page. We found that 22% of them (25 requests) were addressed to the original Magozine.it, 20% (22 requests) were made to Static.xx.fbcdn.net and 13% (14 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Magozine.it.
Page size can be reduced by 877.3 kB (57%)
1.5 MB
664.7 kB
In fact, the total size of Magozine.it main page is 1.5 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. 60% of websites need less resources to load. Javascripts take 744.6 kB which makes up the majority of the site volume.
Potential reduce by 240.0 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 240.0 kB or 89% of the original size.
Potential reduce by 7.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. Mago Zine images are well optimized though.
Potential reduce by 547.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 547.4 kB or 74% of the original size.
Potential reduce by 82.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. Magozine.it needs all CSS files to be minified and compressed as it can save up to 82.5 kB or 80% of the original size.
Number of requests can be reduced by 63 (62%)
101
38
The browser has sent 101 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mago Zine. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
www.magozine.it
2175 ms
shareaholic.js
21 ms
wp-emoji-release.min.js
511 ms
0c390dc0d0a2fb33f3652ca508a0ed18.json
26 ms
fa6a148f_ai1ec_parsed_css.css
1395 ms
styles.css
230 ms
FollowusWidget.css
255 ms
style.css
589 ms
font-awesome.min.css
718 ms
jquery.js
949 ms
jquery-migrate.min.js
408 ms
all.js
163 ms
style.css
209 ms
jquery.form.min.js
231 ms
scripts.js
311 ms
wp-embed.min.js
332 ms
scripts.js
397 ms
social.png
506 ms
12244540_1027915393927585_2594303715997331168_o-191x270.jpg
505 ms
12244540_1027915393927585_2594303715997331168_o1-191x270.jpg
285 ms
12248181_1027915163927608_8744898191959670097_o-191x270.jpg
275 ms
page1-800px-Broken-f18-stop-all-wars-now.pdf-270x135.jpg
285 ms
12087148_947107435328255_6102710217025248262_o-185x270.jpg
506 ms
CK6dV6bWsAAdSs-1-191x270.jpg
402 ms
rodimaglie.jpg
720 ms
IMG_1982-copy-270x180.jpg
548 ms
shrMain.min.js
201 ms
monda-regular-webfont.woff
511 ms
fontawesome-webfont.woff
974 ms
351 ms
xd_arbiter.php
161 ms
xd_arbiter.php
351 ms
jquery.min.js
43 ms
analytics.js
58 ms
pageview.gif
28 ms
like_box.php
298 ms
partners.js
79 ms
sholic.js
12 ms
usermatch
39 ms
beacon.js
12 ms
cms-sh2c.html
66 ms
eexelate.js
17 ms
12 ms
ep
16 ms
ep
16 ms
usermatch
24 ms
ecc
9 ms
33 ms
ca
95 ms
i.gif
151 ms
pixelssl.htm
167 ms
pixel
106 ms
ping_match.gif
55 ms
net.php
35 ms
2964
119 ms
generic
43 ms
pixel
42 ms
casale
40 ms
rum
94 ms
crum
93 ms
generic
49 ms
rum
78 ms
pixel
70 ms
rum
90 ms
McLpmVM3wCm.css
211 ms
VH4VPudaxfN.css
262 ms
Czh0gDTFcBt.css
299 ms
hhn-1r1gAPt.css
370 ms
yz0_I3JB1nk.css
345 ms
tEPQ5ZzKObv.css
338 ms
X97l7PURgJ9.css
379 ms
q68gy-v_YMF.js
411 ms
FJmpeSpHpjS.js
435 ms
0wM5s1Khldu.js
387 ms
1bNoFZUdlYZ.js
386 ms
njO1TPvGzoR.js
433 ms
1QuX41zDRrx.js
434 ms
Oagsvfb4VWi.js
454 ms
LTv6ZK-5zxz.js
534 ms
1FCa-btixu2.js
459 ms
crum
70 ms
ddcssl.htm
83 ms
rs
69 ms
rum
52 ms
match-result
93 ms
xrefid.xgi
19 ms
pixel.gif
61 ms
ermcm
54 ms
pixel.gif
65 ms
crum
17 ms
xrefid.xgi
7 ms
12508756_1014748275232974_717728834048132792_n.jpg
267 ms
safe_image.php
249 ms
12439492_1014746965233105_5416909820350438049_n.jpg
360 ms
12804651_10207639379533815_774425750687976605_n.jpg
368 ms
12311078_10153180889817651_1560056106010795432_n.jpg
369 ms
12549099_457114434484194_375913692611784944_n.jpg
370 ms
12718142_10207494840842544_6006806250870621848_n.jpg
401 ms
12191467_486304921528754_1602892521479055999_n.jpg
400 ms
267579_104523069642856_1770802_n.jpg
539 ms
12794402_10207598076844162_2138905529611380868_n.jpg
441 ms
10353178_1009570682461708_1592907085042455656_n.jpg
450 ms
166591_1740617429490165_3449405569706539759_n.jpg
493 ms
943803_918638291588816_5614930303136646814_n.jpg
635 ms
12801097_990619301022651_7201624602825921961_n.jpg
570 ms
10352413_791216727660205_1485571890088767353_n.jpg
588 ms
wL6VQj7Ab77.png
86 ms
s7jcwEQH7Sx.png
86 ms
QDwYpIaRyfG.png
86 ms
K00K-UgnsKu.png
85 ms
I6-MnjEovm5.js
44 ms
pQrUxxo5oQp.js
79 ms
magozine.it 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
Links do not have a discernible name
magozine.it best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
magozine.it 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
Tap targets are not sized appropriately
IT
IT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Magozine.it can be misinterpreted by Google and other search engines. Our service has detected that Italian is used on the page, and it matches the claimed language. Our system also found out that Magozine.it 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.
magozine.it
Open Graph description is not detected on the main page of Mago Zine. 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: