Tools & Wizards About Us
publicspace.org screenshot

Report Summary

  • 13

    Performance

    Renders faster than
    25% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

publicspace.org

Home - PublicSpace

Page Load Speed

2.8 sec in total

First Response

43 ms

Resources Loaded

2.4 sec

Page Rendered

385 ms

publicspace.org screenshot

About Website

Welcome to publicspace.org homepage info - get ready to check Public Space best content for Spain right away, or after learning these important things about publicspace.org

public space: European Prize for Urban Public Space

Visit publicspace.org

Key Findings

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

Performance Metrics

publicspace.org performance score

13

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.4 s

2/100

10%

LCP (Largest Contentful Paint)

Value9.7 s

0/100

25%

SI (Speed Index)

Value8.0 s

22/100

10%

TBT (Total Blocking Time)

Value1,920 ms

8/100

30%

CLS (Cumulative Layout Shift)

Value0.252

49/100

15%

TTI (Time to Interactive)

Value14.5 s

8/100

10%

Network Requests Diagram

publicspace.org

43 ms

publicspace.org

321 ms

www.publicspace.org

515 ms

gtm.js

108 ms

clay.css

47 ms

Our browser made a total of 65 requests to load all elements on the main page. We found that 77% of them (50 requests) were addressed to the original Publicspace.org, 9% (6 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (748 ms) belongs to the original domain Publicspace.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 162.9 kB (18%)

Content Size

913.2 kB

After Optimization

750.4 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Publicspace.org main page is 913.2 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 45% of websites need less resources to load. Images take 419.4 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 61.4 kB

  • Original 83.0 kB
  • After minification 83.0 kB
  • After compression 21.7 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 61.4 kB or 74% of the original size.

Image Optimization

-11%

Potential reduce by 46.9 kB

  • Original 419.4 kB
  • After minification 372.5 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. Obviously, Public Space needs image optimization as it can save up to 46.9 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-13%

Potential reduce by 54.6 kB

  • Original 410.8 kB
  • After minification 410.8 kB
  • After compression 356.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 54.6 kB or 13% of the original size.

Requests Breakdown

Number of requests can be reduced by 33 (59%)

Requests Now

56

After Optimization

23

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

publicspace.org

publicspace.org

43 ms

publicspace.org

publicspace.org

321 ms

www.publicspace.org

www.publicspace.org

515 ms

gtm.js

gtm.js

108 ms

clay.css

clay.css

47 ms

main.css

main.css

41 ms

combo

combo

426 ms

js_loader_config

js_loader_config

322 ms

combo

combo

599 ms

js_bundle_config

js_bundle_config

349 ms

main.css

main.css

95 ms

css

css

95 ms

css

css

112 ms

jquery-1.11.1.min.js

jquery-1.11.1.min.js

81 ms

jquery-migrate-1.2.1.min.js

jquery-migrate-1.2.1.min.js

96 ms

jquery.ba-bbq.min.js

jquery.ba-bbq.min.js

103 ms

jquery-ui-1.11.1.custom.min.js

jquery-ui-1.11.1.custom.min.js

106 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

112 ms

jquery.carouFredSel-6.2.1-packed.js

jquery.carouFredSel-6.2.1-packed.js

118 ms

jquery.touchSwipe.min.js

jquery.touchSwipe.min.js

119 ms

jquery.transit.min.js

jquery.transit.min.js

129 ms

jquery.sliderControl.js

jquery.sliderControl.js

128 ms

jquery.timeago.js

jquery.timeago.js

137 ms

jquery.hint.js

jquery.hint.js

138 ms

jquery.prettyPhoto.js

jquery.prettyPhoto.js

147 ms

jquery.qtip.min.js

jquery.qtip.min.js

152 ms

jquery.blockUI.js

jquery.blockUI.js

156 ms

markerclusterer.js

markerclusterer.js

162 ms

player.js

player.js

79 ms

odometer.min.js

odometer.min.js

164 ms

js

js

128 ms

email-decode.min.js

email-decode.min.js

99 ms

main.js

main.js

108 ms

vcd15cbe7772f49c399c6a5babf22c1241717689176015

vcd15cbe7772f49c399c6a5babf22c1241717689176015

64 ms

analytics.js

analytics.js

229 ms

logo_publicspace.png

logo_publicspace.png

150 ms

logo_publicspace_img.png

logo_publicspace_img.png

148 ms

menu_arrow.png

menu_arrow.png

149 ms

header_search.png

header_search.png

151 ms

0fba074c-d314-8151-9087-1422fa41664e

0fba074c-d314-8151-9087-1422fa41664e

362 ms

62af40a8-b91b-ee88-29a3-ff4d31d13f38

62af40a8-b91b-ee88-29a3-ff4d31d13f38

450 ms

e925d71a-739e-ad30-08b8-32bad17ab7ed

e925d71a-739e-ad30-08b8-32bad17ab7ed

644 ms

9aee89f4-8998-7c12-bc7e-3465863965bd

9aee89f4-8998-7c12-bc7e-3465863965bd

360 ms

9ed2c542-0b09-9832-0c99-16ef1a249d43

9ed2c542-0b09-9832-0c99-16ef1a249d43

293 ms

666395ec-3e91-03f5-fabe-17384712232c

666395ec-3e91-03f5-fabe-17384712232c

372 ms

11f7804f-7743-22d2-6efd-02539d1e5e9e

11f7804f-7743-22d2-6efd-02539d1e5e9e

426 ms

c495bf9a-3c7a-8631-f79e-65cd805d6935

c495bf9a-3c7a-8631-f79e-65cd805d6935

506 ms

58223669-549e-7a48-7e81-f307c5f4c49a

58223669-549e-7a48-7e81-f307c5f4c49a

504 ms

logo_cccb.png

logo_cccb.png

382 ms

facebook.png

facebook.png

396 ms

twitter.png

twitter.png

405 ms

vimeo.png

vimeo.png

414 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

138 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

138 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

159 ms

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyVVpcBO5Xk.ttf

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyVVpcBO5Xk.ttf

173 ms

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyWyosBO5Xk.ttf

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyWyosBO5Xk.ttf

174 ms

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyXsosBO5Xk.ttf

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyXsosBO5Xk.ttf

174 ms

748 ms

714 ms

navigation_arrow_left.png

navigation_arrow_left.png

319 ms

navigation_arrow_right.png

navigation_arrow_right.png

329 ms

preloader.gif

preloader.gif

339 ms

collect

collect

40 ms

js

js

46 ms

Accessibility Review

publicspace.org accessibility score

79

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA IDs are not unique

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

publicspace.org SEO score

92

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

Links do not have descriptive text

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

publicspace.org

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