8.1 sec in total
1.1 sec
5.3 sec
1.7 sec
Welcome to marymary.gr homepage info - get ready to check Mary best content for Greece right away, or after learning these important things about marymary.gr
To επίσημο blog της Μαρίας Μπακοδήμου με θέματα όπως την ομορφιά, μόδα, showbiz, σεξ και σχέσεις, μαγειρική κτλ
Visit marymary.grWe analyzed Marymary.gr page load time and found that the first response time was 1.1 sec and then it took 7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
marymary.gr performance score
name
value
score
weighting
Value4.6 s
14/100
10%
Value10.5 s
0/100
25%
Value12.0 s
4/100
10%
Value1,410 ms
15/100
30%
Value0.822
4/100
15%
Value29.2 s
0/100
10%
1100 ms
581 ms
6 ms
25 ms
194 ms
Our browser made a total of 186 requests to load all elements on the main page. We found that 68% of them (127 requests) were addressed to the original Marymary.gr, 12% (22 requests) were made to Pbs.twimg.com and 4% (8 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Marymary.gr.
Page size can be reduced by 1.4 MB (16%)
9.1 MB
7.7 MB
In fact, the total size of Marymary.gr main page is 9.1 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 7.7 MB which makes up the majority of the site volume.
Potential reduce by 231.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. 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 231.7 kB or 82% of the original size.
Potential reduce by 393.2 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. Mary images are well optimized though.
Potential reduce by 594.3 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 594.3 kB or 67% of the original size.
Potential reduce by 202.3 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. Marymary.gr needs all CSS files to be minified and compressed as it can save up to 202.3 kB or 85% of the original size.
Number of requests can be reduced by 52 (29%)
182
130
The browser has sent 182 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mary . 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 17 to 1 for CSS and as a result speed up the page load time.
www.marymary.gr
1100 ms
bootstrap.css
581 ms
font-awesome.min.css
6 ms
css
25 ms
flickity.css
194 ms
global.css
291 ms
style.css
196 ms
styles.css
196 ms
jplayer.min.css
382 ms
mCustomScrollbar.min.css
292 ms
polls-css.css
291 ms
style.css
297 ms
wpp.css
300 ms
royalslider.css
300 ms
rs-default-inverted.css
388 ms
rs-content-slider-template.css
389 ms
jquery.js
682 ms
jquery-migrate.min.js
395 ms
jquery.form.min.js
225 ms
scripts.js
192 ms
polls-js.js
192 ms
jquery.royalslider.min.js
443 ms
jquery.js
589 ms
TweenMax.min.js
11 ms
bootstrap.min.js
296 ms
masonry.pkgd.min.js
297 ms
flickity.pkgd.min.js
485 ms
cookieconsent.latest.min.js
441 ms
common.js
442 ms
gpt.js
21 ms
wp-emoji-release.min.js
271 ms
analytics.js
29 ms
pubads_impl_81.js
6 ms
container.html
15 ms
collect
69 ms
logotop.png
125 ms
timthumb.php
408 ms
timthumb.php
422 ms
timthumb.php
603 ms
timthumb.php
393 ms
timthumb.php
407 ms
timthumb.php
631 ms
timthumb.php
602 ms
timthumb.php
494 ms
timthumb.php
631 ms
timthumb.php
631 ms
timthumb.php
630 ms
timthumb.php
792 ms
timthumb.php
878 ms
timthumb.php
807 ms
timthumb.php
730 ms
timthumb.php
806 ms
timthumb.php
808 ms
timthumb.php
909 ms
timthumb.php
968 ms
timthumb.php
997 ms
188409-featured-50x50.jpg
903 ms
187646-featured-50x50.jpg
908 ms
188379-featured-50x50.jpg
975 ms
188686-featured-50x50.jpg
1005 ms
188391-featured-50x50.jpg
1007 ms
timthumb.php
1007 ms
timthumb.php
1064 ms
timthumb.php
1067 ms
ads
67 ms
loading.gif
1075 ms
timthumb.php
1170 ms
timthumb.php
1173 ms
timthumb.php
1160 ms
fontawesome-webfont.woff
15 ms
widgets.js
17 ms
timthumb.php
1193 ms
timthumb.php
1221 ms
30407063369932167
77 ms
ads
31 ms
osd.js
8 ms
timthumb.php
1163 ms
ads
149 ms
18260289149963336880
144 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
24 ms
timthumb.php
993 ms
ads
34 ms
syndication
108 ms
404693491327836160
199 ms
4337284937388104555
22 ms
ads
330 ms
timthumb.php
988 ms
timthumb.php
987 ms
timthumb.php
1040 ms
timthumb.php
1055 ms
timthumb.php
986 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
3 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
6 ms
_________normal.jpg
147 ms
mairi_normal.jpg
169 ms
CcZ4X62UYAAuut4.jpg:small
231 ms
CcZk5v5WwAAsAeZ.jpg:small
234 ms
CcZeFP2W8AEv-PR.jpg:small
229 ms
CcZcLdCWAAIFkbg.jpg:small
229 ms
CcYnj6sVIAABMPM.jpg:small
232 ms
CcYoM5gUUAArKxj.jpg:small
284 ms
CcYXp8BW4AAlEzE.jpg:small
364 ms
CcYUz_UWwAASQvW.jpg:small
316 ms
CcYT53SWwAAJpa8.jpg:small
244 ms
CcYEBzlUsAErWio.jpg:small
361 ms
CcX-m9WWIAANGVC.jpg:small
293 ms
CcX6Nh5W4AEhyGi.jpg:small
361 ms
CcX4_koXEAA1vQV.jpg:small
350 ms
CcX4wMwW0AAVgck.jpg:small
420 ms
CcX4TIzWoAQHzYu.jpg:small
411 ms
CcXwpRPWIAAG1WL.jpg:small
412 ms
CcXsR6RXEAAxEmq.jpg:small
435 ms
CcXpTTQWAAAaa_g.jpg:small
454 ms
CcXlQApWEAAP_vd.jpg:small
438 ms
CcXcd_9WAAAD3up.jpg:small
489 ms
timthumb.php
894 ms
timthumb.php
860 ms
timthumb.php
1054 ms
timthumb.php
918 ms
timthumb.php
944 ms
timthumb.php
940 ms
expansion_embed.js
18 ms
4453312608133794529
13 ms
abg.js
32 ms
m_js_controller.js
38 ms
googlelogo_color_112x36dp.png
62 ms
timthumb.php
851 ms
s
39 ms
x_button_blue2.png
32 ms
timthumb.php
896 ms
timthumb.php
932 ms
timthumb.php
865 ms
timthumb.php
959 ms
jot
31 ms
timthumb.php
801 ms
timthumb.php
955 ms
timthumb.php
961 ms
timthumb.php
1443 ms
timthumb.php
1002 ms
timthumb.php
952 ms
timthumb.php
960 ms
timthumb.php
951 ms
timthumb.php
959 ms
timthumb.php
1112 ms
timthumb.php
990 ms
timthumb.php
991 ms
timthumb.php
971 ms
activeview
13 ms
timthumb.php
973 ms
timthumb.php
960 ms
timthumb.php
959 ms
timthumb.php
999 ms
timthumb.php
933 ms
timthumb.php
962 ms
timthumb.php
949 ms
timthumb.php
967 ms
timthumb.php
920 ms
activeview
13 ms
activeview
14 ms
timthumb.php
896 ms
timthumb.php
874 ms
timthumb.php
875 ms
timthumb.php
1024 ms
timthumb.php
949 ms
timthumb.php
897 ms
timthumb.php
1557 ms
timthumb.php
875 ms
timthumb.php
972 ms
timthumb.php
865 ms
timthumb.php
958 ms
timthumb.php
863 ms
timthumb.php
1016 ms
timthumb.php
903 ms
timthumb.php
879 ms
timthumb.php
1266 ms
timthumb.php
1056 ms
timthumb.php
1000 ms
timthumb.php
976 ms
timthumb.php
1228 ms
search.png
1059 ms
menubg.png
1056 ms
vignette.jpg
973 ms
laikodikastirio.png
1059 ms
vignette-large.jpg
1058 ms
dark-top.css
151 ms
ui
33 ms
marymary.gr 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
[id] attributes on active, focusable elements are not unique
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
marymary.gr 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
Browser errors were logged to the console
marymary.gr 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
Tap targets are not sized appropriately
EL
EL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Marymary.gr can be misinterpreted by Google and other search engines. Our service has detected that Greek is used on the page, and it matches the claimed language. Our system also found out that Marymary.gr 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.
marymary.gr
Open Graph data is detected on the main page of Mary . This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: