Tools & Wizards About Us
ctreal.com screenshot

Report Summary

  • 34

    Performance

    Renders faster than
    54% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

ctreal.com

SmartMLS Inc.

Page Load Speed

2.8 sec in total

First Response

366 ms

Resources Loaded

1.9 sec

Page Rendered

518 ms

ctreal.com screenshot

About Website

Welcome to ctreal.com homepage info - get ready to check Ctreal best content for United States right away, or after learning these important things about ctreal.com

In the Know

Visit ctreal.com

Key Findings

We analyzed Ctreal.com page load time and found that the first response time was 366 ms and then it took 2.4 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

ctreal.com performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

23/100

10%

LCP (Largest Contentful Paint)

Value18.3 s

0/100

25%

SI (Speed Index)

Value10.7 s

7/100

10%

TBT (Total Blocking Time)

Value550 ms

54/100

30%

CLS (Cumulative Layout Shift)

Value0.064

97/100

15%

TTI (Time to Interactive)

Value16.1 s

6/100

10%

Network Requests Diagram

smartmls.com

366 ms

style.min.css

68 ms

css

50 ms

tribe-events-pro-mini-calendar-block.min.css

129 ms

bdt-uikit.css

257 ms

Our browser made a total of 78 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Ctreal.com, 12% (9 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (825 ms) relates to the external source Smartmls.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 118.2 kB (4%)

Content Size

2.8 MB

After Optimization

2.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ctreal.com main page is 2.8 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.0 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 107.4 kB

  • Original 130.6 kB
  • After minification 128.5 kB
  • After compression 23.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 107.4 kB or 82% of the original size.

Image Optimization

-0%

Potential reduce by 714 B

  • 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. Ctreal images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 3.7 kB

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

CSS Optimization

-4%

Potential reduce by 6.4 kB

  • Original 168.0 kB
  • After minification 168.0 kB
  • After compression 161.6 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. Ctreal.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 61 (91%)

Requests Now

67

After Optimization

6

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

smartmls.com

smartmls.com

366 ms

style.min.css

style.min.css

68 ms

css

css

50 ms

tribe-events-pro-mini-calendar-block.min.css

tribe-events-pro-mini-calendar-block.min.css

129 ms

bdt-uikit.css

bdt-uikit.css

257 ms

ep-helper.css

ep-helper.css

194 ms

style-index.css

style-index.css

197 ms

p.css

p.css

194 ms

font-awesome.min.css

font-awesome.min.css

198 ms

tribe-events-single-skeleton.min.css

tribe-events-single-skeleton.min.css

197 ms

tribe-events-single-full.min.css

tribe-events-single-full.min.css

264 ms

widget-base.min.css

widget-base.min.css

264 ms

header-footer-elementor.css

header-footer-elementor.css

265 ms

elementor-icons.min.css

elementor-icons.min.css

266 ms

frontend.min.css

frontend.min.css

325 ms

swiper.min.css

swiper.min.css

318 ms

post-1182.css

post-1182.css

321 ms

frontend.min.css

frontend.min.css

449 ms

post-1868.css

post-1868.css

321 ms

post-1049.css

post-1049.css

323 ms

post-1814.css

post-1814.css

384 ms

css

css

50 ms

fontawesome.min.css

fontawesome.min.css

384 ms

brands.min.css

brands.min.css

389 ms

solid.min.css

solid.min.css

392 ms

jquery.min.js

jquery.min.js

477 ms

jquery-migrate.min.js

jquery-migrate.min.js

447 ms

player.js

player.js

49 ms

p__premium_only.js

p__premium_only.js

477 ms

api.js

api.js

50 ms

js

js

65 ms

all.css

all.css

475 ms

frontend.css

frontend.css

518 ms

style.min.js

style.min.js

612 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

693 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

692 ms

wp-polyfill.min.js

wp-polyfill.min.js

692 ms

index.js

index.js

692 ms

dom-ready.min.js

dom-ready.min.js

692 ms

main.js

main.js

755 ms

ewpe-sharebutton.js

ewpe-sharebutton.js

755 ms

make-column-clickable.js

make-column-clickable.js

753 ms

jquery.smartmenus.min.js

jquery.smartmenus.min.js

697 ms

jquery-numerator.min.js

jquery-numerator.min.js

636 ms

bdt-uikit.min.js

bdt-uikit.min.js

576 ms

webpack.runtime.min.js

webpack.runtime.min.js

592 ms

frontend-modules.min.js

frontend-modules.min.js

666 ms

waypoints.min.js

waypoints.min.js

589 ms

core.min.js

core.min.js

588 ms

frontend.min.js

frontend.min.js

508 ms

helper.min.js

helper.min.js

596 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

595 ms

hooks.min.js

hooks.min.js

598 ms

i18n.min.js

i18n.min.js

597 ms

frontend.min.js

frontend.min.js

546 ms

elements-handlers.min.js

elements-handlers.min.js

578 ms

jquery.sticky.min.js

jquery.sticky.min.js

578 ms

underscore-before.js

underscore-before.js

566 ms

underscore.min.js

underscore.min.js

567 ms

underscore-after.js

underscore-after.js

521 ms

wp-util.min.js

wp-util.min.js

515 ms

frontend.min.js

frontend.min.js

575 ms

recaptcha__en.js

recaptcha__en.js

202 ms

MLS-Login-Button.png

MLS-Login-Button.png

444 ms

ColorLandscape_300dpi-owyscxoezx9xeyq7l4oifk8g9sgt9pvjysybp2mwas.png

ColorLandscape_300dpi-owyscxoezx9xeyq7l4oifk8g9sgt9pvjysybp2mwas.png

467 ms

shutterstock_80320006-scaled.jpg

shutterstock_80320006-scaled.jpg

758 ms

shutterstock_464515616-scaled.jpg

shutterstock_464515616-scaled.jpg

825 ms

app.js

app.js

150 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K0nXBi8Jow.ttf

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K0nXBi8Jow.ttf

70 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K3vXBi8Jow.ttf

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K3vXBi8Jow.ttf

87 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32KxfXBi8Jow.ttf

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32KxfXBi8Jow.ttf

114 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K8nXBi8Jow.ttf

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K8nXBi8Jow.ttf

132 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K0nWBi8Jow.ttf

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K0nWBi8Jow.ttf

134 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K5fQBi8Jow.ttf

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K5fQBi8Jow.ttf

134 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K67QBi8Jow.ttf

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K67QBi8Jow.ttf

134 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K8nQBi8Jow.ttf

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K8nQBi8Jow.ttf

132 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K-DQBi8Jow.ttf

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K-DQBi8Jow.ttf

129 ms

fa-brands-400.woff

fa-brands-400.woff

394 ms

Accessibility Review

ctreal.com accessibility score

95

Accessibility Issues

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.

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

Links do not have a discernible name

Best Practices

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

ctreal.com SEO score

98

Search Engine Optimization Advices

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ctreal.com 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 Ctreal.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

ctreal.com

Open Graph data is detected on the main page of Ctreal. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: