15.5 sec in total
672 ms
14.5 sec
364 ms
Visit pws.gr now to see the best up-to-date PWS content and also check out these interesting facts you probably never knew about pws.gr
Visit pws.grWe analyzed Pws.gr page load time and found that the first response time was 672 ms and then it took 14.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
pws.gr performance score
name
value
score
weighting
Value9.7 s
0/100
10%
Value20.3 s
0/100
25%
Value21.6 s
0/100
10%
Value1,620 ms
12/100
30%
Value0.001
100/100
15%
Value21.1 s
1/100
10%
672 ms
1045 ms
20 ms
385 ms
477 ms
Our browser made a total of 75 requests to load all elements on the main page. We found that 65% of them (49 requests) were addressed to the original Pws.gr, 9% (7 requests) were made to Photoweddingstories.com and 8% (6 requests) were made to Translate.googleapis.com. The less responsive or slowest element that took the longest time to load (5.2 sec) relates to the external source Photoweddingstories.gr.
Page size can be reduced by 1.1 MB (33%)
3.3 MB
2.2 MB
In fact, the total size of Pws.gr main page is 3.3 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. 50% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.
Potential reduce by 37.2 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 37.2 kB or 78% of the original size.
Potential reduce by 69.6 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. PWS images are well optimized though.
Potential reduce by 733.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 733.6 kB or 63% of the original size.
Potential reduce by 264.6 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. Pws.gr needs all CSS files to be minified and compressed as it can save up to 264.6 kB or 83% of the original size.
Number of requests can be reduced by 50 (69%)
72
22
The browser has sent 72 CSS, Javascripts, AJAX and image requests in order to completely render the main page of PWS. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 39 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
photoweddingstories.com
672 ms
wp-emoji-release.min.js
1045 ms
jquery-ui.css
20 ms
validationEngine.jquery.css
385 ms
styles.css
477 ms
settings.css
813 ms
dynamic-captions.css
662 ms
static-captions.css
538 ms
plugin.styles.css
525 ms
jquery-ui-1.10.3.custom.min.css
838 ms
kad-slider.css
1134 ms
virtue.css
1716 ms
default.css
763 ms
css
32 ms
jquery.js
1211 ms
jquery-migrate.min.js
913 ms
core.min.js
945 ms
gmshc.2.3.min.js
1054 ms
js
33 ms
jquery.themepunch.plugins.min.js
1482 ms
jquery.themepunch.revolution.min.js
1449 ms
jquery.maskedinput.min.js
1228 ms
widget.min.js
1324 ms
mouse.min.js
1455 ms
draggable.min.js
1453 ms
slider.min.js
1456 ms
iris.min.js
1672 ms
plupload.full.min.js
2105 ms
script.js
1796 ms
modernizr.min.js
1979 ms
jquery.colorbox-min.js
1795 ms
element.js
37 ms
datepicker.min.js
1892 ms
jquery.form.min.js
1919 ms
scripts.js
1912 ms
jquery.blockUI.min.js
378 ms
woocommerce.min.js
2177 ms
jquery.cookie.min.js
1173 ms
cart-fragments.min.js
3140 ms
kadence-slider-min.js
2352 ms
masonry.min.js
2066 ms
plugins-min.js
2359 ms
main.js
2067 ms
kt-add-to-cart-variation-min.js
2217 ms
wp-embed.min.js
2214 ms
css
15 ms
facebook-e1408614873809.png
5156 ms
xv.png
228 ms
ios-linen.jpg
1178 ms
logo-pws1.png
235 ms
3418-1943-lyd_7918.jpg
735 ms
3486-2222-ant_pap007.jpg
911 ms
3428-1945-fiq_8979_copy_copy1.jpg
667 ms
3506-1943-weddingsameday.jpg
829 ms
3392-2222-02_1.jpg
636 ms
3454-2222-the_fhater_1.jpg
908 ms
3425-2222-brideparty.jpg
980 ms
translateelement.css
68 ms
main.js
98 ms
fontawesome-webfont.woff
873 ms
loader.gif
1076 ms
element_main.js
41 ms
photoweddingstories.com
1490 ms
nav_arrows.png
164 ms
slide_direction.png
144 ms
translate_24dp.png
25 ms
l
48 ms
googlelogo_color_68x28dp.png
3 ms
cleardot.gif
34 ms
te_ctrl3.gif
13 ms
loading.gif
20 ms
common.js
5 ms
util.js
19 ms
stats.js
17 ms
AuthenticationService.Authenticate
166 ms
pws.gr accessibility score
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
pws.gr 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
Missing source maps for large first-party JavaScript
pws.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
Document doesn't have a valid hreflang
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
EL
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pws.gr can be misinterpreted by Google and other search engines. Our service has detected that Greek is used on the page, and it does not match the claimed English language. Our system also found out that Pws.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.
pws.gr
Open Graph description is not detected on the main page of PWS. 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: