Tools & Wizards About Us
trace.me screenshot

Report Summary

  • 35

    Performance

    Renders faster than
    55% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

trace.me

KCS TraceME - Keep track of your most valued assets and people

Page Load Speed

2.7 sec in total

First Response

280 ms

Resources Loaded

2.2 sec

Page Rendered

196 ms

trace.me screenshot

About Website

Welcome to trace.me homepage info - get ready to check Trace best content for United States right away, or after learning these important things about trace.me

500,000 TraceME units sold, Dutch quality & 35 years experience, Modular end devices & Fully customizable

Visit trace.me

Key Findings

We analyzed Trace.me page load time and found that the first response time was 280 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

trace.me performance score

35

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.3 s

7/100

10%

LCP (Largest Contentful Paint)

Value15.3 s

0/100

25%

SI (Speed Index)

Value11.6 s

4/100

10%

TBT (Total Blocking Time)

Value310 ms

77/100

30%

CLS (Cumulative Layout Shift)

Value0.192

64/100

15%

TTI (Time to Interactive)

Value13.3 s

12/100

10%

Network Requests Diagram

trace.me

280 ms

home

423 ms

bootstrap.min.css

217 ms

font-awesome.min.css

311 ms

animate.min.css

377 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that 92% of them (54 requests) were addressed to the original Trace.me, 3% (2 requests) were made to Fonts.gstatic.com and 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Trace.me.

Page Optimization Overview & Recommendations

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

Content Size

1.1 MB

After Optimization

879.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Trace.me main page is 1.1 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. 55% of websites need less resources to load. Images take 571.0 kB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 57.8 kB

  • Original 64.9 kB
  • After minification 56.4 kB
  • After compression 7.1 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. This page needs HTML code to be minified as it can gain 8.5 kB, which is 13% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 57.8 kB or 89% of the original size.

Image Optimization

-0%

Potential reduce by 657 B

  • Original 571.0 kB
  • After minification 570.3 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. Trace images are well optimized though.

JavaScript Optimization

-25%

Potential reduce by 66.7 kB

  • Original 265.6 kB
  • After minification 265.6 kB
  • After compression 198.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 66.7 kB or 25% of the original size.

CSS Optimization

-39%

Potential reduce by 66.0 kB

  • Original 169.6 kB
  • After minification 169.5 kB
  • After compression 103.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. Trace.me needs all CSS files to be minified and compressed as it can save up to 66.0 kB or 39% of the original size.

Requests Breakdown

Number of requests can be reduced by 42 (79%)

Requests Now

53

After Optimization

11

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

trace.me

trace.me

280 ms

home

home

423 ms

bootstrap.min.css

bootstrap.min.css

217 ms

font-awesome.min.css

font-awesome.min.css

311 ms

animate.min.css

animate.min.css

377 ms

simple-line-icons.min.css

simple-line-icons.min.css

374 ms

owl.carousel.min.css

owl.carousel.min.css

381 ms

owl.theme.default.min.css

owl.theme.default.min.css

386 ms

magnific-popup.min.css

magnific-popup.min.css

384 ms

theme.css

theme.css

414 ms

theme-elements.css

theme-elements.css

578 ms

theme-blog.css

theme-blog.css

464 ms

theme-shop.css

theme-shop.css

469 ms

settings.css

settings.css

479 ms

layers.css

layers.css

585 ms

navigation.css

navigation.css

509 ms

component.css

component.css

551 ms

default.css

default.css

663 ms

custom.css

custom.css

565 ms

modernizr.min.js

modernizr.min.js

596 ms

style.switcher.js

style.switcher.js

640 ms

css

css

52 ms

jquery.min.js

jquery.min.js

794 ms

jquery.appear.min.js

jquery.appear.min.js

712 ms

jquery.easing.min.js

jquery.easing.min.js

712 ms

jquery-cookie.min.js

jquery-cookie.min.js

713 ms

bootstrap.min.js

bootstrap.min.js

791 ms

common.min.js

common.min.js

792 ms

jquery.validation.min.js

jquery.validation.min.js

792 ms

jquery.easy-pie-chart.min.js

jquery.easy-pie-chart.min.js

791 ms

jquery.gmap.min.js

jquery.gmap.min.js

792 ms

jquery.lazyload.min.js

jquery.lazyload.min.js

838 ms

jquery.isotope.min.js

jquery.isotope.min.js

859 ms

owl.carousel.min.js

owl.carousel.min.js

875 ms

jquery.magnific-popup.min.js

jquery.magnific-popup.min.js

872 ms

vide.min.js

vide.min.js

871 ms

theme.js

theme.js

885 ms

jquery.themepunch.tools.min.js

jquery.themepunch.tools.min.js

1046 ms

conveythis-initializer.js

conveythis-initializer.js

41 ms

js

js

84 ms

jquery.themepunch.revolution.min.js

jquery.themepunch.revolution.min.js

1092 ms

jquery.flipshow.min.js

jquery.flipshow.min.js

750 ms

view.home.js

view.home.js

657 ms

view.contact.js

view.contact.js

599 ms

theme.init.js

theme.init.js

699 ms

examples.portfolio.js

examples.portfolio.js

680 ms

logo-white.png

logo-white.png

354 ms

slide5.jpg

slide5.jpg

560 ms

fltmangt2.jpg

fltmangt2.jpg

615 ms

slide6.jpg

slide6.jpg

638 ms

klimmen.jpg

klimmen.jpg

560 ms

topseller.jpg

topseller.jpg

557 ms

dutchqualitu.jpg

dutchqualitu.jpg

558 ms

map.jpg

map.jpg

654 ms

font

font

18 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

565 ms

font

font

41 ms

Simple-Line-Icons.ttf

Simple-Line-Icons.ttf

535 ms

revicons.woff

revicons.woff

154 ms

Accessibility Review

trace.me accessibility score

66

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

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

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

trace.me best practices score

75

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

trace.me SEO score

83

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

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Trace.me 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 Trace.me 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

trace.me

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