Report Summary

  • 27

    Performance

    Renders faster than
    47% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 78% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

bullseye.eu

Werken in nederland | Bullseye Uitzendbureau B.V. | Gelderland

Page Load Speed

1.1 sec in total

First Response

134 ms

Resources Loaded

919 ms

Page Rendered

86 ms

bullseye.eu screenshot

About Website

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

Wij zijn Bullseye Uitzendbureau. Ons kantoor is gevestigd in een prachtig pand in het mooie Beek (bij Nijmegen). Een team van enthousiaste, ambitieuze en gedreven medewerkers staat dagelijks voor u kl...

Visit bullseye.eu

Key Findings

We analyzed Bullseye.eu page load time and found that the first response time was 134 ms and then it took 1 sec 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

bullseye.eu performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

79/100

10%

LCP (Largest Contentful Paint)

Value6.2 s

11/100

25%

SI (Speed Index)

Value9.7 s

10/100

10%

TBT (Total Blocking Time)

Value3,870 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value17.3 s

4/100

10%

Network Requests Diagram

bullseye.eu

134 ms

www.bullseyeuitzendbureau.nl

138 ms

bt

80 ms

require.min.js

58 ms

main-r.min.js

42 ms

Our browser made a total of 39 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Bullseye.eu, 72% (28 requests) were made to Static.parastorage.com and 15% (6 requests) were made to Frog.wix.com. The less responsive or slowest element that took the longest time to load (458 ms) relates to the external source Static.wixstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.9 MB (76%)

Content Size

2.5 MB

After Optimization

613.4 kB

In fact, the total size of Bullseye.eu main page is 2.5 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. 70% of websites need less resources to load. Javascripts take 2.5 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 23.1 kB

  • Original 29.8 kB
  • After minification 29.6 kB
  • After compression 6.8 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 23.1 kB or 77% of the original size.

JavaScript Optimization

-76%

Potential reduce by 1.9 MB

  • Original 2.5 MB
  • After minification 2.5 MB
  • After compression 604.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 1.9 MB or 76% of the original size.

CSS Optimization

-77%

Potential reduce by 5.8 kB

  • Original 7.5 kB
  • After minification 6.0 kB
  • After compression 1.7 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. Bullseye.eu needs all CSS files to be minified and compressed as it can save up to 5.8 kB or 77% of the original size.

Requests Breakdown

Number of requests can be reduced by 32 (86%)

Requests Now

37

After Optimization

5

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

Accessibility Review

bullseye.eu accessibility score

91

Accessibility Issues

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

Buttons do not have an accessible name

High

Links do not have a discernible name

Best Practices

bullseye.eu best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

bullseye.eu SEO score

100

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

Language and Encoding

  • Language Detected

    NL

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Bullseye.eu can be misinterpreted by Google and other search engines. Our service has detected that Dutch 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 Bullseye.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

Open Graph data is detected on the main page of PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this: