2.3 sec in total
437 ms
1.5 sec
393 ms
Click here to check amazing Public Space content. Otherwise, check out these important facts you probably never knew about publicspace.in
abcd
Visit publicspace.inWe analyzed Publicspace.in page load time and found that the first response time was 437 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
publicspace.in performance score
name
value
score
weighting
Value3.3 s
40/100
10%
Value8.0 s
2/100
25%
Value6.0 s
46/100
10%
Value530 ms
55/100
30%
Value0
100/100
15%
Value6.2 s
62/100
10%
437 ms
228 ms
267 ms
181 ms
163 ms
Our browser made a total of 52 requests to load all elements on the main page. We found that 69% of them (36 requests) were addressed to the original Publicspace.in, 4% (2 requests) were made to Wd-edge.sharethis.com and 4% (2 requests) were made to T.sharethis.com. The less responsive or slowest element that took the longest time to load (785 ms) belongs to the original domain Publicspace.in.
Page size can be reduced by 336.2 kB (18%)
1.9 MB
1.5 MB
In fact, the total size of Publicspace.in main page is 1.9 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. 35% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 26.9 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 26.9 kB or 84% of the original size.
Potential reduce by 67.6 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. Public Space images are well optimized though.
Potential reduce by 188.7 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 188.7 kB or 72% of the original size.
Potential reduce by 53.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. Publicspace.in needs all CSS files to be minified and compressed as it can save up to 53.0 kB or 85% of the original size.
Number of requests can be reduced by 14 (29%)
49
35
The browser has sent 49 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 6 to 1 for JavaScripts and as a result speed up the page load time.
publicspace.in
437 ms
style.css
228 ms
jquery.min.js
267 ms
jquery.fancybox-1.3.4.pack.js
181 ms
jquery.fancybox-1.3.4.css
163 ms
buttons.js
7 ms
jquery.masonry.min.js
46 ms
header_bg.jpg
168 ms
logo.png
171 ms
submitad.png
170 ms
sellAdd.jpg
173 ms
1408011839.jpg
405 ms
1408026796.jpg
785 ms
televisiontab.png
170 ms
mobilestab.png
171 ms
bicyclestab.png
172 ms
appliancestab.png
173 ms
paintings-tab.png
173 ms
clothes-tab.png
173 ms
furnituretab.png
178 ms
babygoodtab.png
180 ms
1401275056.png
240 ms
findads_bg.png
239 ms
2.png
199 ms
1.jpg
200 ms
3.jpg
240 ms
4.jpg
260 ms
6.jpg
286 ms
7.jpg
285 ms
8.jpg
280 ms
fllowusbg.jpg
298 ms
D376B979-5C7B-4FF6-C871-2AE4B732808F.it.fwoff.v13.sAL2.h0.o0
369 ms
getAllAppDefault.esi
120 ms
footerbg.png
278 ms
fancybox-x.png
185 ms
fancybox.png
244 ms
fancybox-y.png
294 ms
blank.gif
294 ms
getSegment.php
156 ms
checkOAuth.esi
21 ms
t.dhj
23 ms
t.dhj
20 ms
cm
41 ms
x35248
106 ms
s-3271.xgi
40 ms
11 ms
hbpix
73 ms
7 ms
xrefid.xgi
4 ms
pixel
19 ms
pixel
14 ms
2981
27 ms
publicspace.in accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
<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
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
publicspace.in best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
publicspace.in SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Document uses legible font sizes
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Publicspace.in 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 Publicspace.in 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.
publicspace.in
Open Graph data is detected on the main page of Public Space. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: