Tools & Wizards About Us
publicsearch.eu screenshot

Report Summary

  • 88

    Performance

    Renders faster than
    90% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

publicsearch.eu

PublicSearch.eu – PublicSearch Europe. Company Registers EU, USA, Offshore

Page Load Speed

918 ms in total

First Response

8 ms

Resources Loaded

661 ms

Page Rendered

249 ms

publicsearch.eu screenshot

About Website

Welcome to publicsearch.eu homepage info - get ready to check Public Search best content right away, or after learning these important things about publicsearch.eu

Public Search Belgium. Company registers

Visit publicsearch.eu

Key Findings

We analyzed Publicsearch.eu page load time and found that the first response time was 8 ms and then it took 910 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

publicsearch.eu performance score

88

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

57/100

10%

LCP (Largest Contentful Paint)

Value2.9 s

80/100

25%

SI (Speed Index)

Value2.8 s

96/100

10%

TBT (Total Blocking Time)

Value130 ms

96/100

30%

CLS (Cumulative Layout Shift)

Value0.007

100/100

15%

TTI (Time to Interactive)

Value4.3 s

85/100

10%

Network Requests Diagram

publicsearch.eu

8 ms

publicsearch.eu

32 ms

webfont.js

108 ms

jetpack-likes.css

124 ms

131 ms

Our browser made a total of 71 requests to load all elements on the main page. We found that 42% of them (30 requests) were addressed to the original Publicsearch.eu, 15% (11 requests) were made to S0.wp.com and 14% (10 requests) were made to Fonts.wp.com. The less responsive or slowest element that took the longest time to load (411 ms) belongs to the original domain Publicsearch.eu.

Page Optimization Overview & Recommendations

Page size can be reduced by 149.7 kB (44%)

Content Size

336.8 kB

After Optimization

187.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Publicsearch.eu main page is 336.8 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. 50% of websites need less resources to load. HTML takes 207.1 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 148.4 kB

  • Original 207.1 kB
  • After minification 204.3 kB
  • After compression 58.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 148.4 kB or 72% of the original size.

Image Optimization

-1%

Potential reduce by 202 B

  • Original 15.2 kB
  • After minification 15.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. Public Search images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 790 B

  • Original 92.5 kB
  • After minification 92.5 kB
  • After compression 91.8 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

-1%

Potential reduce by 306 B

  • Original 21.9 kB
  • After minification 21.9 kB
  • After compression 21.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. Publicsearch.eu has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 53 (90%)

Requests Now

59

After Optimization

6

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

publicsearch.eu

publicsearch.eu

8 ms

publicsearch.eu

publicsearch.eu

32 ms

webfont.js

webfont.js

108 ms

jetpack-likes.css

jetpack-likes.css

124 ms

131 ms

124 ms

coblocks-style.css

coblocks-style.css

128 ms

123 ms

136 ms

css

css

152 ms

124 ms

rlt-proxy.js

rlt-proxy.js

122 ms

hovercards.min.js

hovercards.min.js

133 ms

wpgroho.js

wpgroho.js

124 ms

119 ms

grunion.css

grunion.css

136 ms

138 ms

index.min.js

index.min.js

137 ms

index.min.js

index.min.js

132 ms

137 ms

w.js

w.js

137 ms

css

css

58 ms

global-print.css

global-print.css

2 ms

20px-belgium.svg_.png

20px-belgium.svg_.png

347 ms

wpcom-gray-white.png

wpcom-gray-white.png

62 ms

master.html

master.html

66 ms

g.gif

g.gif

100 ms

remote-login.php

remote-login.php

141 ms

20px-flag_of_austria.svg_.png

20px-flag_of_austria.svg_.png

141 ms

fa773-flag_of_bulgaria.svg_.png

fa773-flag_of_bulgaria.svg_.png

128 ms

3a05b-flag_of_croatia.svg_.png

3a05b-flag_of_croatia.svg_.png

127 ms

35a9a-flag_of_cyprus.svg_.png

35a9a-flag_of_cyprus.svg_.png

128 ms

20px-flag_of_the_czech_republic.svg_.png

20px-flag_of_the_czech_republic.svg_.png

126 ms

2bde0-20px-flag_of_denmark.svg_.png

2bde0-20px-flag_of_denmark.svg_.png

140 ms

aa21c-20px-flag_of_estonia.svg_.png

aa21c-20px-flag_of_estonia.svg_.png

173 ms

99e92-flag_of_finland.svg_.png

99e92-flag_of_finland.svg_.png

197 ms

3de89-flag_of_france.svg_.png

3de89-flag_of_france.svg_.png

193 ms

flag_of_germany.svg_.png

flag_of_germany.svg_.png

180 ms

flag_of_greece.svg_.png

flag_of_greece.svg_.png

261 ms

flag_of_hungary.svg_.png

flag_of_hungary.svg_.png

275 ms

cee07-20px-flag_of_ireland.svg_.png

cee07-20px-flag_of_ireland.svg_.png

229 ms

06879-flag_of_italy.svg_.png

06879-flag_of_italy.svg_.png

258 ms

flag_of_latvia.svg_.png

flag_of_latvia.svg_.png

246 ms

20px-flag_of_lithuania.svg_.png

20px-flag_of_lithuania.svg_.png

308 ms

d0031-20px-flag_of_luxembourg.svg_.png

d0031-20px-flag_of_luxembourg.svg_.png

298 ms

20px-flag_of_malta.svg_.png

20px-flag_of_malta.svg_.png

308 ms

02feb-20px-flag_of_the_netherlands.svg_.png

02feb-20px-flag_of_the_netherlands.svg_.png

302 ms

9d67d-flag_of_poland.svg_.png

9d67d-flag_of_poland.svg_.png

333 ms

2f86b-flag_of_portugal.svg_.png

2f86b-flag_of_portugal.svg_.png

360 ms

00b06-20px-flag_of_romania.svg_.png

00b06-20px-flag_of_romania.svg_.png

379 ms

12f31-20px-flag_of_slovakia.svg_.png

12f31-20px-flag_of_slovakia.svg_.png

411 ms

f5741-20px-flag_of_slovenia.svg_.png

f5741-20px-flag_of_slovenia.svg_.png

336 ms

33c71-flag_of_spain.svg_.png

33c71-flag_of_spain.svg_.png

378 ms

a2df0-flag_of_sweden.svg_.png

a2df0-flag_of_sweden.svg_.png

403 ms

0d703-flag_of_the_united_kingdom.svg_.png

0d703-flag_of_the_united_kingdom.svg_.png

395 ms

g.gif

g.gif

103 ms

g.gif

g.gif

104 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4gaVc.ttf

70 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

65 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

70 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

82 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

70 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

82 ms

5aUz9_-1phKLFgshYDvh6Vwt7VRtuA.ttf

5aUz9_-1phKLFgshYDvh6Vwt7VRtuA.ttf

82 ms

5aUu9_-1phKLFgshYDvh6Vwt5eFIqER2jg.ttf

5aUu9_-1phKLFgshYDvh6Vwt5eFIqER2jg.ttf

82 ms

5aUt9_-1phKLFgshYDvh6Vwt7V9dsW1W.ttf

5aUt9_-1phKLFgshYDvh6Vwt7V9dsW1W.ttf

83 ms

5aUo9_-1phKLFgshYDvh6Vwt7V9VBEhGh09D.ttf

5aUo9_-1phKLFgshYDvh6Vwt7V9VBEhGh09D.ttf

83 ms

rlt-proxy.js

rlt-proxy.js

38 ms

38 ms

actionbar.css

actionbar.css

2 ms

actionbar.js

actionbar.js

9 ms

Accessibility Review

publicsearch.eu accessibility score

94

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.

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

publicsearch.eu best practices score

83

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

Page has valid source maps

SEO Factors

publicsearch.eu SEO score

91

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

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 Publicsearch.eu 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 Publicsearch.eu 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

publicsearch.eu

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