Tools & Wizards About Us
iprofile.org screenshot

Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 84% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 71

    SEO

    Google-friendlier than
    30% of websites

iprofile.org

iProfile Pty Ltd | Recruitment Software | CV Database Cleansing

Page Load Speed

16.1 sec in total

First Response

1 sec

Resources Loaded

9.5 sec

Page Rendered

5.5 sec

iprofile.org screenshot

About Website

Welcome to iprofile.org homepage info - get ready to check IProfile best content for Australia right away, or after learning these important things about iprofile.org

Our powerful technology helps recruiters realise the full value of their own CV database. Find out what a difference a current and up-to-date CV database could make to your recruitment agency?.

Visit iprofile.org

Key Findings

We analyzed Iprofile.org page load time and found that the first response time was 1 sec and then it took 15 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

iprofile.org performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

51/100

10%

LCP (Largest Contentful Paint)

Value13.3 s

0/100

25%

SI (Speed Index)

Value6.1 s

45/100

10%

TBT (Total Blocking Time)

Value1,350 ms

17/100

30%

CLS (Cumulative Layout Shift)

Value0.037

100/100

15%

TTI (Time to Interactive)

Value12.8 s

13/100

10%

Network Requests Diagram

iprofile.org

1048 ms

style.css

237 ms

blue.css

50 ms

css

52 ms

jquery.fancybox-1.3.4.css

50 ms

Our browser made a total of 64 requests to load all elements on the main page. We found that 75% of them (48 requests) were addressed to the original Iprofile.org, 6% (4 requests) were made to Google-analytics.com and 6% (4 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (2.6 sec) relates to the external source Static.doubleclick.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.6 MB (54%)

Content Size

3.0 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Iprofile.org main page is 3.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. 70% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 19.4 kB

  • Original 26.5 kB
  • After minification 24.7 kB
  • After compression 7.1 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 19.4 kB or 73% of the original size.

Image Optimization

-36%

Potential reduce by 567.3 kB

  • Original 1.6 MB
  • After minification 1.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. Obviously, IProfile needs image optimization as it can save up to 567.3 kB or 36% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-67%

Potential reduce by 522.0 kB

  • Original 775.3 kB
  • After minification 714.6 kB
  • After compression 253.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 522.0 kB or 67% of the original size.

CSS Optimization

-83%

Potential reduce by 503.5 kB

  • Original 608.5 kB
  • After minification 590.2 kB
  • After compression 105.0 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. Iprofile.org needs all CSS files to be minified and compressed as it can save up to 503.5 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 26 (43%)

Requests Now

61

After Optimization

35

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

iprofile.org

iprofile.org

1048 ms

style.css

style.css

237 ms

blue.css

blue.css

50 ms

css

css

52 ms

jquery.fancybox-1.3.4.css

jquery.fancybox-1.3.4.css

50 ms

style.css

style.css

84 ms

jquery.min.js

jquery.min.js

101 ms

domassistant.js

domassistant.js

85 ms

selectivizr.js

selectivizr.js

85 ms

slides.min.jquery.js

slides.min.jquery.js

85 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

84 ms

jquery.cycle.min.js

jquery.cycle.min.js

99 ms

jquery.fancybox-1.3.4.js

jquery.fancybox-1.3.4.js

99 ms

jquery.validate.min.js

jquery.validate.min.js

150 ms

scripts.js

scripts.js

149 ms

wp-embed.min.js

wp-embed.min.js

149 ms

reset.css

reset.css

148 ms

screen.css

screen.css

150 ms

custom.css

custom.css

148 ms

master.css

master.css

11 ms

analytics.js

analytics.js

775 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

375 ms

ga.js

ga.js

232 ms

iprofile_logo6.png

iprofile_logo6.png

1354 ms

bg-body.png

bg-body.png

484 ms

bg-masthead.png

bg-masthead.png

506 ms

bg-masthead-inner.png

bg-masthead-inner.png

505 ms

bg-nav.png

bg-nav.png

503 ms

iprofile_cv_database_before2.png

iprofile_cv_database_before2.png

506 ms

bg-button.png

bg-button.png

504 ms

bg-button.png

bg-button.png

537 ms

iprofile_cv_database_after.png

iprofile_cv_database_after.png

489 ms

logos6.png

logos6.png

537 ms

slider-arrows.png

slider-arrows.png

538 ms

bg-breadcrumbs.png

bg-breadcrumbs.png

587 ms

bg-slidenav.png

bg-slidenav.png

538 ms

plus_48.png

plus_48.png

538 ms

block_48.png

block_48.png

538 ms

search_48.png

search_48.png

537 ms

buy_48.png

buy_48.png

584 ms

bg-button-small.png

bg-button-small.png

583 ms

bg-bottom.png

bg-bottom.png

585 ms

bg-bottom-widget.png

bg-bottom-widget.png

582 ms

bg-footer.png

bg-footer.png

585 ms

twitter.png

twitter.png

584 ms

linkedin.png

linkedin.png

584 ms

youtube.png

youtube.png

584 ms

home0.png

home0.png

581 ms

home1.png

home1.png

583 ms

home2.png

home2.png

537 ms

vxMs7sSPtCY

vxMs7sSPtCY

1535 ms

collect

collect

471 ms

__utm.gif

__utm.gif

59 ms

print.css

print.css

57 ms

arrow-down.png

arrow-down.png

180 ms

www-player-vflMqr8uC.css

www-player-vflMqr8uC.css

67 ms

www-embed-player.js

www-embed-player.js

288 ms

base.js

base.js

473 ms

id

id

1811 ms

XXcU61IQc85IUvBk15C2mErkR9crdcNuTkaKRvq8LQg.js

XXcU61IQc85IUvBk15C2mErkR9crdcNuTkaKRvq8LQg.js

2389 ms

ad_status.js

ad_status.js

2594 ms

logo_ringo-vflOpz8ZI.png

logo_ringo-vflOpz8ZI.png

1128 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

805 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

828 ms

Accessibility Review

iprofile.org accessibility score

94

Accessibility Issues

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

<frame> or <iframe> elements do not have a title

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

iprofile.org best practices score

67

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

iprofile.org SEO score

71

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

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 Iprofile.org 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 Iprofile.org 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

iprofile.org

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