Tools & Wizards About Us
ifelse.com screenshot

Report Summary

  • 100

    Performance

    Renders faster than
    97% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 55

    SEO

    Google-friendlier than
    20% of websites

ifelse.com

Escrow Pay - Escrow.com

Page Load Speed

3.3 sec in total

First Response

690 ms

Resources Loaded

2.3 sec

Page Rendered

264 ms

ifelse.com screenshot

About Website

Click here to check amazing Ifelse content. Otherwise, check out these important facts you probably never knew about ifelse.com

Escrow.com provides the best online escrow transaction services and accounts that facilitate and accelerate e-commerce by assuring a secure settlement.

Visit ifelse.com

Key Findings

We analyzed Ifelse.com page load time and found that the first response time was 690 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

ifelse.com performance score

100

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0.6 s

100/100

10%

LCP (Largest Contentful Paint)

Value0.6 s

100/100

25%

SI (Speed Index)

Value0.6 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value0.6 s

100/100

10%

Network Requests Diagram

details.php4

690 ms

jquery-ui.css

340 ms

gtld.buyers.css

325 ms

forms.css

348 ms

iehacks.css

346 ms

Our browser made a total of 82 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Ifelse.com, 12% (10 requests) were made to Sedo.com and 2% (2 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (713 ms) relates to the external source Code.etracker.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.4 MB (67%)

Content Size

2.1 MB

After Optimization

690.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ifelse.com main page is 2.1 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.1 MB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 206.6 kB

  • Original 233.2 kB
  • After minification 230.7 kB
  • After compression 26.6 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 206.6 kB or 89% of the original size.

Image Optimization

-9%

Potential reduce by 26.4 kB

  • Original 303.4 kB
  • After minification 277.0 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. Ifelse images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 774.2 kB

  • Original 1.1 MB
  • After minification 894.4 kB
  • After compression 309.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 774.2 kB or 71% of the original size.

CSS Optimization

-83%

Potential reduce by 386.4 kB

  • Original 463.4 kB
  • After minification 369.9 kB
  • After compression 77.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. Ifelse.com needs all CSS files to be minified and compressed as it can save up to 386.4 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 56 (69%)

Requests Now

81

After Optimization

25

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

details.php4

details.php4

690 ms

jquery-ui.css

jquery-ui.css

340 ms

gtld.buyers.css

gtld.buyers.css

325 ms

forms.css

forms.css

348 ms

iehacks.css

iehacks.css

346 ms

basic.css

basic.css

377 ms

clickelements.css

clickelements.css

359 ms

slide.css

slide.css

348 ms

basemod_common.css

basemod_common.css

355 ms

basemod_layout0102.css

basemod_layout0102.css

362 ms

content_correction.css

content_correction.css

361 ms

content_common.css

content_common.css

385 ms

web_new.css

web_new.css

391 ms

contentstyle6.css

contentstyle6.css

383 ms

navigation.css

navigation.css

387 ms

print_common.css

print_common.css

389 ms

magicsuggest.css

magicsuggest.css

395 ms

tld-dialog.css

tld-dialog.css

394 ms

base_additional.css

base_additional.css

398 ms

tx_news_additional.css

tx_news_additional.css

394 ms

googlefonts.css

googlefonts.css

413 ms

font-awesome-4.css

font-awesome-4.css

402 ms

sedo.offerpage.css

sedo.offerpage.css

418 ms

sedo.plusbox.css

sedo.plusbox.css

403 ms

sedoDialogTip.css

sedoDialogTip.css

403 ms

selectric.css

selectric.css

414 ms

jquery.js

jquery.js

445 ms

jquery-ui.js

jquery-ui.js

526 ms

gtld.buyers.js

gtld.buyers.js

422 ms

modernizr.js

modernizr.js

421 ms

etracker.js

etracker.js

422 ms

langselect.js

langselect.js

428 ms

selectbox.js

selectbox.js

432 ms

core.js

core.js

434 ms

magicsuggest.js

magicsuggest.js

433 ms

tld-dialog.js

tld-dialog.js

457 ms

jquery.dialogTip.js

jquery.dialogTip.js

457 ms

font-awesome.min.css

font-awesome.min.css

34 ms

e.js

e.js

634 ms

swfobject.js

swfobject.js

156 ms

override.css

override.css

154 ms

buttons.css

buttons.css

138 ms

forms.js

forms.js

133 ms

jquery.thickbox.js

jquery.thickbox.js

135 ms

jquery.getUrlParam.js

jquery.getUrlParam.js

140 ms

jquery.timers-1.2.js

jquery.timers-1.2.js

129 ms

jquery.dialogBox.js

jquery.dialogBox.js

128 ms

nNav.js

nNav.js

136 ms

slide.js

slide.js

134 ms

functions.js

functions.js

119 ms

navigation.js

navigation.js

118 ms

offerpage.js

offerpage.js

114 ms

selectric.js

selectric.js

122 ms

bg_pagetop.gif

bg_pagetop.gif

37 ms

gpt.js

gpt.js

19 ms

ga.js

ga.js

144 ms

pubads_impl_82.js

pubads_impl_82.js

83 ms

jquery.js

jquery.js

253 ms

630 ms

t.js

t.js

713 ms

logo-sedo.png

logo-sedo.png

78 ms

BuyDomains_BrowseCategories_V2.jpg

BuyDomains_BrowseCategories_V2.jpg

191 ms

sprites.main.png

sprites.main.png

146 ms

Sedo-Logo.png

Sedo-Logo.png

71 ms

sprites.buttons.png

sprites.buttons.png

73 ms

bg_contentbase.png

bg_contentbase.png

73 ms

details.js

details.js

239 ms

sedo.sprites.offerpage.png

sedo.sprites.offerpage.png

49 ms

sedo.sprites.png

sedo.sprites.png

50 ms

sedo.sprites.search.png

sedo.sprites.search.png

49 ms

secure-seals.png

secure-seals.png

50 ms

payment-options.png

payment-options.png

51 ms

container.html

container.html

127 ms

common.php

common.php

249 ms

common.php

common.php

261 ms

service.php

service.php

354 ms

sprites.partner.logos.png

sprites.partner.logos.png

49 ms

yes.gif

yes.gif

48 ms

exclamation-mark.png

exclamation-mark.png

48 ms

domaining-com.gif

domaining-com.gif

336 ms

loader.gif

loader.gif

336 ms

__utm.gif

__utm.gif

31 ms

Accessibility Review

ifelse.com accessibility score

68

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

Document doesn't have a <title> element

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

Best Practices

ifelse.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

ifelse.com SEO score

55

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

Document doesn't have a <title> element

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    US

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ifelse.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is . Our system also found out that Ifelse.com 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

ifelse.com

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