Tools & Wizards About Us
wefreeze.net screenshot

Report Summary

  • 39

    Performance

    Renders faster than
    58% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 0

    Best Practices

  • 93

    SEO

    Google-friendlier than
    83% of websites

wefreeze.net

Wedding Photographer in Malaysia | Wefreeze Photography

Page Load Speed

8.2 sec in total

First Response

552 ms

Resources Loaded

6.9 sec

Page Rendered

734 ms

wefreeze.net screenshot

About Website

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.net

Key Findings

We analyzed Wefreeze.net page load time and found that the first response time was 552 ms and then it took 7.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

wefreeze.net performance score

39

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.7 s

0/100

10%

LCP (Largest Contentful Paint)

Value17.9 s

0/100

25%

SI (Speed Index)

Value10.3 s

8/100

10%

TBT (Total Blocking Time)

Value330 ms

75/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value15.5 s

7/100

10%

Network Requests Diagram

wefreeze.net

552 ms

wefreeze.net

1253 ms

wp-emoji-release.min.js

247 ms

sbi-styles.min.css

489 ms

style.min.css

716 ms

Our browser made a total of 63 requests to load all elements on the main page. We found that 97% of them (61 requests) were addressed to the original Wefreeze.net, 2% (1 request) were made to Google.com and 2% (1 request) were made to Gstatic.com. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain Wefreeze.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 140.9 kB (5%)

Content Size

2.7 MB

After Optimization

2.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Wefreeze.net main page is 2.7 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. Images take 2.0 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 112.4 kB

  • Original 135.4 kB
  • After minification 127.8 kB
  • After compression 23.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 112.4 kB or 83% of the original size.

Image Optimization

-1%

Potential reduce by 15.0 kB

  • Original 2.0 MB
  • After minification 2.0 MB

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.

JavaScript Optimization

-2%

Potential reduce by 10.7 kB

  • Original 474.4 kB
  • After minification 474.4 kB
  • After compression 463.7 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. This website has mostly compressed JavaScripts.

CSS Optimization

-4%

Potential reduce by 2.7 kB

  • Original 68.0 kB
  • After minification 67.8 kB
  • After compression 65.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. Wefreeze.net has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 41 (71%)

Requests Now

58

After Optimization

17

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 58 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 13 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

wefreeze.net

wefreeze.net

552 ms

wefreeze.net

wefreeze.net

1253 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

247 ms

sbi-styles.min.css

sbi-styles.min.css

489 ms

style.min.css

style.min.css

716 ms

classic-themes.min.css

classic-themes.min.css

719 ms

styles.css

styles.css

725 ms

jquery-ui.min.css

jquery-ui.min.css

731 ms

flo-forms-public.min.css

flo-forms-public.min.css

732 ms

fontello.css

fontello.css

739 ms

style.css

style.css

954 ms

flo-core-icons.css

flo-core-icons.css

958 ms

vendor.css

vendor.css

968 ms

style.min.css

style.min.css

1217 ms

style.css

style.css

972 ms

jquery.min.js

jquery.min.js

1233 ms

jquery-migrate.min.js

jquery-migrate.min.js

1192 ms

jquery.validate.min.js

jquery.validate.min.js

1199 ms

flo-forms-public.js

flo-forms-public.js

1210 ms

jquery.bind-first-0.2.3.min.js

jquery.bind-first-0.2.3.min.js

1232 ms

js.cookie-2.1.3.min.js

js.cookie-2.1.3.min.js

1431 ms

public.js

public.js

1438 ms

sbi-scripts.min.js

sbi-scripts.min.js

1933 ms

akismet-frontend.js

akismet-frontend.js

1459 ms

index.js

index.js

1458 ms

index.js

index.js

1474 ms

core.min.js

core.min.js

1670 ms

datepicker.min.js

datepicker.min.js

1679 ms

jquery.colorbox-min.js

jquery.colorbox-min.js

1701 ms

scripts.js

scripts.js

1704 ms

comment-reply.min.js

comment-reply.min.js

1721 ms

vendor.js

vendor.js

2149 ms

scripts.min.js

scripts.min.js

1919 ms

api.js

api.js

61 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

1945 ms

wp-polyfill.min.js

wp-polyfill.min.js

1949 ms

index.js

index.js

1970 ms

flo-icons.css

flo-icons.css

953 ms

sbi-sprite.png

sbi-sprite.png

358 ms

Wedding-in-Boathouse.jpg

Wedding-in-Boathouse.jpg

495 ms

Maternity-photo-in-KL.jpg

Maternity-photo-in-KL.jpg

957 ms

Pre-wedding-at-Thean-Hou-Temple.jpg

Pre-wedding-at-Thean-Hou-Temple.jpg

1231 ms

Pre-wedding-in-studio.jpg

Pre-wedding-in-studio.jpg

740 ms

librecaslondisplay-regular.ttf

librecaslondisplay-regular.ttf

976 ms

OldStandard-Regular.ttf

OldStandard-Regular.ttf

1423 ms

flo-icons.woff

flo-icons.woff

718 ms

recaptcha__en.js

recaptcha__en.js

108 ms

admin-ajax.php

admin-ajax.php

2675 ms

overlay.png

overlay.png

757 ms

wefreeze-logo-2018-header.png

wefreeze-logo-2018-header.png

245 ms

wefreeze-logo-2018-header-white.png

wefreeze-logo-2018-header-white.png

240 ms

LOGO-WEB.png

LOGO-WEB.png

244 ms

malaysia-wedding-photography_84-533x800.jpg

malaysia-wedding-photography_84-533x800.jpg

253 ms

Charlie-Cherlyn_132-600x400.jpg

Charlie-Cherlyn_132-600x400.jpg

249 ms

Perth-Wedding-in-Caversham-house_130-533x800.jpg

Perth-Wedding-in-Caversham-house_130-533x800.jpg

487 ms

wedding-in-danna-hotel-langkawi_132-533x800.jpg

wedding-in-danna-hotel-langkawi_132-533x800.jpg

488 ms

new-zealand-pre-wedding-_01-600x400.jpg

new-zealand-pre-wedding-_01-600x400.jpg

486 ms

1128_Malaysia-weddding-photographer-533x800.jpg

1128_Malaysia-weddding-photographer-533x800.jpg

497 ms

193_Malaysia-wedding-photography-533x800.jpg

193_Malaysia-wedding-photography-533x800.jpg

504 ms

122_boathouse-wedding-533x800.jpg

122_boathouse-wedding-533x800.jpg

731 ms

119_ART.jpg

119_ART.jpg

1443 ms

fb-icon.png

fb-icon.png

735 ms

insta-icon.png

insta-icon.png

741 ms

Accessibility Review

wefreeze.net accessibility score

80

Accessibility Issues

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

High

ARIA input fields do not have accessible names

High

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

High

Buttons do not have an accessible name

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

SEO Factors

wefreeze.net SEO score

93

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    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.

Social Sharing Optimization

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: