Tools & Wizards About Us
wemakeapps.net screenshot

Report Summary

  • 53

    Performance

    Renders faster than
    70% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

wemakeapps.net

We Make Apps - App developers in Melbourne, Australia

Page Load Speed

16.9 sec in total

First Response

610 ms

Resources Loaded

16 sec

Page Rendered

296 ms

wemakeapps.net screenshot

About Website

Visit wemakeapps.net now to see the best up-to-date We Make Apps content and also check out these interesting facts you probably never knew about wemakeapps.net

We Make Apps is an app design and development company in Melbourne, Australia. developing iOS, Android and desktop apps.

Visit wemakeapps.net

Key Findings

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

Performance Metrics

wemakeapps.net performance score

53

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

19/100

10%

LCP (Largest Contentful Paint)

Value17.6 s

0/100

25%

SI (Speed Index)

Value7.1 s

31/100

10%

TBT (Total Blocking Time)

Value190 ms

91/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value7.0 s

53/100

10%

Network Requests Diagram

wemakeapps.net

610 ms

main.css

503 ms

folio.css

501 ms

stylesheet.css

501 ms

modernizr-2.6.2-respond-1.1.0.min.js

514 ms

Our browser made a total of 80 requests to load all elements on the main page. We found that 88% of them (70 requests) were addressed to the original Wemakeapps.net, 8% (6 requests) were made to Maps.googleapis.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (4.6 sec) belongs to the original domain Wemakeapps.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 690.0 kB (7%)

Content Size

9.5 MB

After Optimization

8.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Wemakeapps.net main page is 9.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. 55% of websites need less resources to load. Images take 8.6 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 26.1 kB

  • Original 32.9 kB
  • After minification 25.9 kB
  • After compression 6.8 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. This page needs HTML code to be minified as it can gain 7.0 kB, which is 21% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 26.1 kB or 79% of the original size.

Image Optimization

-2%

Potential reduce by 164.7 kB

  • Original 8.6 MB
  • After minification 8.4 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. We Make Apps images are well optimized though.

JavaScript Optimization

-57%

Potential reduce by 383.3 kB

  • Original 673.2 kB
  • After minification 655.9 kB
  • After compression 289.9 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 383.3 kB or 57% of the original size.

CSS Optimization

-83%

Potential reduce by 115.9 kB

  • Original 139.7 kB
  • After minification 116.2 kB
  • After compression 23.9 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. Wemakeapps.net needs all CSS files to be minified and compressed as it can save up to 115.9 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 34 (44%)

Requests Now

77

After Optimization

43

  • Images
  • JavaScript
  • CSS

The browser has sent 77 CSS, Javascripts, AJAX and image requests in order to completely render the main page of We Make Apps. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

wemakeapps.net

wemakeapps.net

610 ms

main.css

main.css

503 ms

folio.css

folio.css

501 ms

stylesheet.css

stylesheet.css

501 ms

modernizr-2.6.2-respond-1.1.0.min.js

modernizr-2.6.2-respond-1.1.0.min.js

514 ms

jquery.min.js

jquery.min.js

41 ms

js

js

55 ms

tile.stamen.js

tile.stamen.js

74 ms

jquery.sequence-min.js

jquery.sequence-min.js

519 ms

jquery.scrollTo-1.4.3.1-min.js

jquery.scrollTo-1.4.3.1-min.js

519 ms

waypoints.min.js

waypoints.min.js

740 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

740 ms

jquery.validate.min.js

jquery.validate.min.js

741 ms

jquery.form.min.js

jquery.form.min.js

742 ms

jquery.placeholder.min.js

jquery.placeholder.min.js

766 ms

jquery.easytabs.min.js

jquery.easytabs.min.js

765 ms

ilightbox.packed.js

ilightbox.packed.js

1239 ms

jquery.touchSwipe.min.js

jquery.touchSwipe.min.js

985 ms

css_browser_selector.min.js

css_browser_selector.min.js

985 ms

main.js

main.js

987 ms

normalize.min.css

normalize.min.css

524 ms

ilightbox.css

ilightbox.css

530 ms

font-awesome.min.css

font-awesome.min.css

747 ms

skin.css

skin.css

252 ms

skin.css

skin.css

252 ms

skin.css

skin.css

255 ms

skin.css

skin.css

253 ms

skin.css

skin.css

465 ms

skin.css

skin.css

468 ms

skin.css

skin.css

500 ms

skin.css

skin.css

501 ms

loader.gif

loader.gif

500 ms

melbourne.svg

melbourne.svg

749 ms

sequencejsnav_black.png

sequencejsnav_black.png

503 ms

arrowmiddle_left.png

arrowmiddle_left.png

503 ms

arrowmiddle_right.png

arrowmiddle_right.png

503 ms

logo.svg

logo.svg

504 ms

hero.png

hero.png

3055 ms

hero.png

hero.png

2508 ms

sep_dark.png

sep_dark.png

755 ms

tile.jpg

tile.jpg

1507 ms

tile.jpg

tile.jpg

1504 ms

tile.jpg

tile.jpg

1498 ms

tile.jpg

tile.jpg

1504 ms

tile.jpg

tile.jpg

1749 ms

tile.jpg

tile.jpg

2016 ms

tile.jpg

tile.jpg

1758 ms

tile.jpg

tile.jpg

2018 ms

tile.jpg

tile.jpg

2253 ms

client-logo.png

client-logo.png

2015 ms

app_store.png

app_store.png

2266 ms

play_store.png

play_store.png

2268 ms

hero.png

hero.png

3802 ms

dulux-logo.png

dulux-logo.png

2505 ms

hbt-logo.png

hbt-logo.png

2514 ms

hero.png

hero.png

3545 ms

espn-logo.png

espn-logo.png

2751 ms

hero.png

hero.png

3775 ms

storeplay-logo.png

storeplay-logo.png

2763 ms

hero.png

hero.png

3511 ms

mortgage-choice-logo.png

mortgage-choice-logo.png

3038 ms

jr-logo.png

jr-logo.png

3290 ms

hero.png

hero.png

3557 ms

ploytech-logo.png

ploytech-logo.png

3542 ms

hero.png

hero.png

4013 ms

hero.png

hero.png

4551 ms

ga.js

ga.js

61 ms

close_mobile_slide.png

close_mobile_slide.png

3637 ms

__utm.gif

__utm.gif

12 ms

caecilia-roman-bold.woff

caecilia-roman-bold.woff

3325 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

3531 ms

withbgr.png

withbgr.png

3562 ms

picons03.png

picons03.png

3562 ms

picons06.png

picons06.png

3569 ms

picons40.png

picons40.png

3521 ms

common.js

common.js

5 ms

map.js

map.js

16 ms

util.js

util.js

36 ms

marker.js

marker.js

36 ms

onion.js

onion.js

13 ms

Accessibility Review

wemakeapps.net accessibility score

73

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

wemakeapps.net best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

wemakeapps.net SEO score

90

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wemakeapps.net can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Wemakeapps.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

wemakeapps.net

Open Graph description is not detected on the main page of We Make Apps. 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: