Tools & Wizards About Us
cpipg.com screenshot

Report Summary

  • 58

    Performance

    Renders faster than
    74% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

cpipg.com

Home | CPIPG

Page Load Speed

5.2 sec in total

First Response

419 ms

Resources Loaded

3.3 sec

Page Rendered

1.5 sec

cpipg.com screenshot

About Website

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

CPI Property Group (CPIPG) is one of the largest owners of income-generating real estate in Europe.

Visit cpipg.com

Key Findings

We analyzed Cpipg.com page load time and found that the first response time was 419 ms and then it took 4.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

cpipg.com performance score

58

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.7 s

92/100

10%

LCP (Largest Contentful Paint)

Value5.5 s

19/100

25%

SI (Speed Index)

Value14.6 s

1/100

10%

TBT (Total Blocking Time)

Value110 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value35.0 s

0/100

10%

Network Requests Diagram

cpipg.com

419 ms

cpipg.com

470 ms

en

888 ms

site.css

109 ms

media.css

214 ms

Our browser made a total of 31 requests to load all elements on the main page. We found that all of those requests were addressed to Cpipg.com and no external sources were called. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Cpipg.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 142.0 kB (1%)

Content Size

14.4 MB

After Optimization

14.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-85%

Potential reduce by 110.7 kB

  • Original 131.0 kB
  • After minification 100.9 kB
  • After compression 20.3 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 30.1 kB, which is 23% 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 110.7 kB or 85% of the original size.

Image Optimization

-0%

Potential reduce by 26.8 kB

  • Original 14.2 MB
  • After minification 14.1 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. CPIPG images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 1.4 kB

  • Original 90.8 kB
  • After minification 90.8 kB
  • After compression 89.4 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

-8%

Potential reduce by 3.1 kB

  • Original 37.1 kB
  • After minification 37.1 kB
  • After compression 34.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. Cpipg.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 3 (13%)

Requests Now

24

After Optimization

21

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

cpipg.com

cpipg.com

419 ms

cpipg.com

cpipg.com

470 ms

en

en

888 ms

site.css

site.css

109 ms

media.css

media.css

214 ms

plugins.css

plugins.css

301 ms

CPIPG_logo_RGB.svg

CPIPG_logo_RGB.svg

297 ms

5fd24ef60f6d0138042939.svg

5fd24ef60f6d0138042939.svg

296 ms

5fd24f220224b751529175.svg

5fd24f220224b751529175.svg

294 ms

5fd24fa33160b985513519.svg

5fd24fa33160b985513519.svg

295 ms

61238fb21670a528296920.svg

61238fb21670a528296920.svg

378 ms

plugins.js

plugins.js

593 ms

main.js

main.js

395 ms

framework.combined-min.js

framework.combined-min.js

393 ms

framework.extras-min.css

framework.extras-min.css

395 ms

thumb_3235_610_610_0_0_crop.jpg

thumb_3235_610_610_0_0_crop.jpg

811 ms

thumb_1700_610_610_0_0_crop.jpeg

thumb_1700_610_610_0_0_crop.jpeg

811 ms

thumb_1702_610_610_0_0_crop.jpeg

thumb_1702_610_610_0_0_crop.jpeg

873 ms

thumb_3301_694_694_0_0_crop.jpg

thumb_3301_694_694_0_0_crop.jpg

875 ms

thumb_3185_694_694_0_0_crop.jpg

thumb_3185_694_694_0_0_crop.jpg

877 ms

thumb_3118_694_694_0_0_crop.jpeg

thumb_3118_694_694_0_0_crop.jpeg

884 ms

5fd24ef2761c5709031134.jpg

5fd24ef2761c5709031134.jpg

565 ms

5fd329a903ddf524578143.png

5fd329a903ddf524578143.png

1144 ms

5fd32abda8c40652148051.png

5fd32abda8c40652148051.png

1230 ms

6596aeeaea3e4620841612.jpeg

6596aeeaea3e4620841612.jpeg

1137 ms

key-numbers-homepage-bg-23-11.png

key-numbers-homepage-bg-23-11.png

765 ms

footer-bg.png

footer-bg.png

668 ms

eb7705ea-a2f4-430f-8ec4-e19bed44faa0.woff

eb7705ea-a2f4-430f-8ec4-e19bed44faa0.woff

614 ms

f5576b8a-3e10-4121-acc4-278c312dc9c8.woff

f5576b8a-3e10-4121-acc4-278c312dc9c8.woff

713 ms

3c37170b-5bb4-4009-92d9-d046a8e64480.woff

3c37170b-5bb4-4009-92d9-d046a8e64480.woff

730 ms

6bddaa10-510f-4bd5-8741-eb2fd346c748.woff

6bddaa10-510f-4bd5-8741-eb2fd346c748.woff

811 ms

Accessibility Review

cpipg.com accessibility score

78

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.

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

Links do not have a discernible name

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.

Best Practices

cpipg.com 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

SEO Factors

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

    N/A

  • Encoding

    UTF-8

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

cpipg.com

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