Tools & Wizards About Us
codesearch.co.uk screenshot

Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 60

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

codesearch.co.uk

Codesearch: Data Science & AI Recruitment | Codesearch

Page Load Speed

3.4 sec in total

First Response

147 ms

Resources Loaded

2.6 sec

Page Rendered

620 ms

codesearch.co.uk screenshot

About Website

Visit codesearch.co.uk now to see the best up-to-date Codesearch content and also check out these interesting facts you probably never knew about codesearch.co.uk

Codesearch are an International Data Science & AI Recruitment Consultancy. We find our candidates the positions they want, not fit them into roles we alr...

Visit codesearch.co.uk

Key Findings

We analyzed Codesearch.co.uk page load time and found that the first response time was 147 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

codesearch.co.uk performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

50/100

10%

LCP (Largest Contentful Paint)

Value13.0 s

0/100

25%

SI (Speed Index)

Value6.7 s

37/100

10%

TBT (Total Blocking Time)

Value430 ms

64/100

30%

CLS (Cumulative Layout Shift)

Value0.764

5/100

15%

TTI (Time to Interactive)

Value10.9 s

21/100

10%

Network Requests Diagram

codesearch.co.uk

147 ms

codesearch.co.uk

334 ms

www.codesearch.co.uk

614 ms

analytics.js

31 ms

logo.png

95 ms

Our browser made a total of 48 requests to load all elements on the main page. We found that 52% of them (25 requests) were addressed to the original Codesearch.co.uk, 21% (10 requests) were made to I.guim.co.uk and 10% (5 requests) were made to Api.nowsignage.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Codesearch.co.uk.

Page Optimization Overview & Recommendations

Page size can be reduced by 422.8 kB (7%)

Content Size

5.9 MB

After Optimization

5.5 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Codesearch.co.uk main page is 5.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. 85% 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 5.3 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 413.3 kB

  • Original 512.3 kB
  • After minification 510.5 kB
  • After compression 99.0 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 413.3 kB or 81% of the original size.

Image Optimization

-0%

Potential reduce by 9.4 kB

  • Original 5.3 MB
  • After minification 5.3 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. Codesearch images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 54 B

  • Original 93.0 kB
  • After minification 93.0 kB
  • After compression 92.9 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.

Requests Breakdown

Number of requests can be reduced by 8 (19%)

Requests Now

42

After Optimization

34

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

codesearch.co.uk

codesearch.co.uk

147 ms

codesearch.co.uk

codesearch.co.uk

334 ms

www.codesearch.co.uk

www.codesearch.co.uk

614 ms

analytics.js

analytics.js

31 ms

logo.png

logo.png

95 ms

menu-button.png

menu-button.png

99 ms

shutterstock_436945282%2011.09.33.jpg

shutterstock_436945282%2011.09.33.jpg

94 ms

shutterstock_264802244.jpg

shutterstock_264802244.jpg

93 ms

shutterstock_497643985.jpg

shutterstock_497643985.jpg

97 ms

shutterstock_567712279.jpg

shutterstock_567712279.jpg

1549 ms

pattern.png

pattern.png

106 ms

Tamara.jpg

Tamara.jpg

94 ms

Rob%20Koeling%20Picture.jfif

Rob%20Koeling%20Picture.jfif

108 ms

Alexis%20Renaudin.jpg

Alexis%20Renaudin.jpg

96 ms

Hatice.jpeg

Hatice.jpeg

110 ms

Julian.jpg

Julian.jpg

112 ms

Gamal.jpeg

Gamal.jpeg

107 ms

css

css

92 ms

css

css

95 ms

js

js

107 ms

application_universal.js

application_universal.js

109 ms

application_focus.js

application_focus.js

105 ms

application_candidate_dashboard.js

application_candidate_dashboard.js

106 ms

application_recruiter_dashboard.js

application_recruiter_dashboard.js

225 ms

application_job_search.js

application_job_search.js

224 ms

application.js

application.js

108 ms

logo-footer.png

logo-footer.png

224 ms

volcanic-logo.png

volcanic-logo.png

222 ms

collect

collect

140 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

116 ms

js

js

122 ms

rax-HiSdp9cPL3KIF7xrJDs.woff

rax-HiSdp9cPL3KIF7xrJDs.woff

81 ms

S6uyw4BMUTPHjx4wWA.woff

S6uyw4BMUTPHjx4wWA.woff

95 ms

1fff52b82bc9ec73f555ce5da5a1bfd6

1fff52b82bc9ec73f555ce5da5a1bfd6

191 ms

8c90811a172e87770f8435b6d0d2a18d

8c90811a172e87770f8435b6d0d2a18d

183 ms

c095f956a5c7d2c9c4fdbbc4b5b09662

c095f956a5c7d2c9c4fdbbc4b5b09662

206 ms

a5be43f41b5dee2f59f783fc82c6cfcd

a5be43f41b5dee2f59f783fc82c6cfcd

191 ms

056c985ec7f8c2127fe3375c17766fa8

056c985ec7f8c2127fe3375c17766fa8

185 ms

4017.jpg

4017.jpg

49 ms

4928.jpg

4928.jpg

265 ms

1847.jpg

1847.jpg

86 ms

3500.jpg

3500.jpg

88 ms

5810.jpg

5810.jpg

87 ms

1760.jpg

1760.jpg

146 ms

4128.jpg

4128.jpg

316 ms

2948.jpg

2948.jpg

89 ms

1815.jpg

1815.jpg

597 ms

580.jpg

580.jpg

534 ms

Accessibility Review

codesearch.co.uk accessibility score

60

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-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[aria-*] attributes do not have valid values

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

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

codesearch.co.uk 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

SEO Factors

codesearch.co.uk SEO score

77

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

High

Image elements do not have [alt] attributes

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

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Codesearch.co.uk 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 Codesearch.co.uk main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

codesearch.co.uk

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