11.3 sec in total
2.1 sec
9.1 sec
126 ms
Welcome to wefreeze.net homepage info - get ready to check Wefreeze best content right away, or after learning these important things about wefreeze.net
Malaysia Wedding Photographer | Wefreeze Photography | We create light-filled & airy photographs, capturing the essence of beauty in simplicity.
Visit wefreeze.netWe analyzed Wefreeze.net page load time and found that the first response time was 2.1 sec and then it took 9.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
wefreeze.net performance score
name
value
score
weighting
Value9.6 s
0/100
10%
Value58.0 s
0/100
25%
Value17.1 s
0/100
10%
Value310 ms
77/100
30%
Value0
100/100
15%
Value31.6 s
0/100
10%
2051 ms
14 ms
470 ms
483 ms
492 ms
Our browser made a total of 65 requests to load all elements on the main page. We found that 68% of them (44 requests) were addressed to the original Wefreeze.net, 5% (3 requests) were made to Fonts.googleapis.com and 5% (3 requests) were made to S7.addthis.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Wefreeze.net.
Page size can be reduced by 1.0 MB (53%)
2.0 MB
921.8 kB
In fact, the total size of Wefreeze.net main page is 2.0 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. 55% of websites need less resources to load. Javascripts take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 113.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 113.2 kB or 79% of the original size.
Potential reduce by 5.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. Wefreeze images are well optimized though.
Potential reduce by 853.2 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 853.2 kB or 69% of the original size.
Potential reduce by 76.2 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. Wefreeze.net needs all CSS files to be minified and compressed as it can save up to 76.2 kB or 81% of the original size.
Number of requests can be reduced by 37 (65%)
57
20
The browser has sent 57 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wefreeze. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
wefreeze.net
2051 ms
css
14 ms
reset.css
470 ms
text.css
483 ms
960.css
492 ms
shortcodes.css
493 ms
orbit-1.2.3.css
496 ms
style.css
922 ms
font-awesome.min.css
6 ms
css
15 ms
style-white.css
705 ms
nivo-slider.css
723 ms
custom.php
1743 ms
styles.css
513 ms
jquery-ui.css
8 ms
form.min.css
520 ms
jquery.js
1451 ms
jquery-migrate.min.js
736 ms
core.min.js
760 ms
datepicker.min.js
1259 ms
underscore.min.js
926 ms
form.min.js
977 ms
jquery.easing.1.3.js
1006 ms
jquery.nivo.slider.pack.js
1160 ms
custom.js
1219 ms
jquery.scrollTo-1.4.2-min.js
1254 ms
single-horizontal.js
1391 ms
on.js
31 ms
addthis_widget.js
10 ms
jquery.form.min.js
1236 ms
scripts.js
1279 ms
api.js
19 ms
backbone.min.js
1282 ms
wp-api.js
1422 ms
wp-embed.min.js
1460 ms
css
39 ms
analytics.js
67 ms
wp-emoji-release.min.js
251 ms
pre-wedding-in-Penang_36-280x280.jpg
250 ms
pre-wedding-in-Malaysia_71-280x280.jpg
245 ms
Screen-Shot-2017-09-02-at-10.21.01-PM-280x280.png
991 ms
Mathan-Cherlene_45-280x280.jpg
293 ms
Syahm-Nava_06-280x280.jpg
351 ms
Screen-Shot-2017-06-29-at-11.08.35-AM-280x280.png
1451 ms
Gavin-Way-Yee_02-280x280.jpg
725 ms
Jeremy-Jia-Yin_70-280x280.jpg
741 ms
logo.jpg
1673 ms
zoom-in.png
581 ms
next-post.png
816 ms
facebook.png
963 ms
instagram.png
986 ms
recaptcha__en.js
50 ms
collect
24 ms
FJNab1jzp1t7ctjNl8ugHCZ2oysoEQEeKwjgmXLRnTc.ttf
18 ms
x-font-woff;charset=utf-8;base64,
1 ms
fontawesome-webfont.woff
18 ms
_ate.track.config_resp
9 ms
300lo.json
60 ms
sh.48536d49e4da3bdba54606b4.html
19 ms
layers.0ee9c4d64cf5ebc35dab.js
16 ms
pixel
17 ms
pixel
13 ms
match-result
3 ms
wefreeze.net
1282 ms
wefreeze.net
1524 ms
wefreeze.net 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 input fields do not have accessible names
ARIA toggle fields do not have accessible names
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
Buttons do not have an accessible name
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
wefreeze.net SEO score
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 Wefreeze.net 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 Wefreeze.net 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.
wefreeze.net
Open Graph data is detected on the main page of Wefreeze. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: