Tools & Wizards About Us
graebel.com screenshot

Report Summary

  • 34

    Performance

    Renders faster than
    54% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

graebel.com

Graebel | Global Relocation Services & Mobility Solutions

Page Load Speed

3.1 sec in total

First Response

80 ms

Resources Loaded

2.5 sec

Page Rendered

576 ms

graebel.com screenshot

About Website

Click here to check amazing Graebel content for United States. Otherwise, check out these important facts you probably never knew about graebel.com

Graebel provides global relocation services & exceptional mobility experiences for your employees anywhere in the world.

Visit graebel.com

Key Findings

We analyzed Graebel.com page load time and found that the first response time was 80 ms and then it took 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

graebel.com performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

57/100

10%

LCP (Largest Contentful Paint)

Value4.4 s

38/100

25%

SI (Speed Index)

Value6.6 s

38/100

10%

TBT (Total Blocking Time)

Value5,240 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value19.3 s

2/100

10%

Network Requests Diagram

graebel.com

80 ms

www.graebel.com

81 ms

www.graebel.com

1077 ms

button.css

25 ms

simpay-public.min.css

28 ms

Our browser made a total of 60 requests to load all elements on the main page. We found that 67% of them (40 requests) were addressed to the original Graebel.com, 5% (3 requests) were made to Googletagmanager.com and 3% (2 requests) were made to Unpkg.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Graebel.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 122.1 kB (15%)

Content Size

799.9 kB

After Optimization

677.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Graebel.com main page is 799.9 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. 65% of websites need less resources to load. Images take 357.3 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 122.1 kB

  • Original 146.2 kB
  • After minification 100.0 kB
  • After compression 24.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 46.2 kB, which is 32% 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 122.1 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 357.3 kB
  • After minification 357.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. Graebel images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 8 B

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

-0%

Potential reduce by 60 B

  • Original 79.2 kB
  • After minification 79.2 kB
  • After compression 79.1 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. Graebel.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 31 (62%)

Requests Now

50

After Optimization

19

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

graebel.com

graebel.com

80 ms

www.graebel.com

www.graebel.com

81 ms

www.graebel.com

www.graebel.com

1077 ms

button.css

button.css

25 ms

simpay-public.min.css

simpay-public.min.css

28 ms

simpay-public-pro.min.css

simpay-public-pro.min.css

191 ms

public.css

public.css

144 ms

app.css

app.css

300 ms

jquery.min.js

jquery.min.js

36 ms

jquery-migrate.min.js

jquery-migrate.min.js

46 ms

28 ms

flickity.pkgd.min.js

flickity.pkgd.min.js

32 ms

vendor.js

vendor.js

66 ms

app.js

app.js

60 ms

lazyload.min.js

lazyload.min.js

65 ms

flickity.pkgd.min.js

flickity.pkgd.min.js

25 ms

gtm.js

gtm.js

155 ms

icon-arrow.svg

icon-arrow.svg

123 ms

logo.svg

logo.svg

121 ms

build-your-global-mobility-program.svg

build-your-global-mobility-program.svg

119 ms

plus.svg

plus.svg

118 ms

icon-relocate-50px.svg

icon-relocate-50px.svg

119 ms

icon-graebel-difference-50px.svg

icon-graebel-difference-50px.svg

123 ms

icon-explore-50px.svg

icon-explore-50px.svg

125 ms

icon-access-50px.svg

icon-access-50px.svg

124 ms

icon-tailor-engage-50px.svg

icon-tailor-engage-50px.svg

126 ms

icon-managing-cadence-50px.svg

icon-managing-cadence-50px.svg

128 ms

linkedin.svg

linkedin.svg

127 ms

youtube.svg

youtube.svg

232 ms

logo-x.svg

logo-x.svg

177 ms

facebook.svg

facebook.svg

129 ms

privacyoptions29x14.png

privacyoptions29x14.png

176 ms

DINOT-Italic.otf

DINOT-Italic.otf

112 ms

DINOT-LightItalic.otf

DINOT-LightItalic.otf

113 ms

DINOT-Medium.ttf

DINOT-Medium.ttf

113 ms

DINOT-Regular.ttf

DINOT-Regular.ttf

212 ms

DINOT-Light.ttf

DINOT-Light.ttf

185 ms

DINOT-Bold.ttf

DINOT-Bold.ttf

113 ms

EE-journey-thumbnail.jpg

EE-journey-thumbnail.jpg

299 ms

Custom_Solutions_1200x800-380x268.jpg

Custom_Solutions_1200x800-380x268.jpg

60 ms

Single-Point-of-Care_1200x800-380x268.jpg

Single-Point-of-Care_1200x800-380x268.jpg

60 ms

Commitment-Sustainability_1200x800-380x268.jpg

Commitment-Sustainability_1200x800-380x268.jpg

105 ms

Local-Support-Global-Partners_1200x800-1.jpg

Local-Support-Global-Partners_1200x800-1.jpg

78 ms

people-first.jpg

people-first.jpg

60 ms

js

js

94 ms

destination

destination

220 ms

insight.min.js

insight.min.js

268 ms

uwt.js

uwt.js

249 ms

fbevents.js

fbevents.js

261 ms

6ruta54stszh.js

6ruta54stszh.js

306 ms

be9637bf87c89b33.min.js

be9637bf87c89b33.min.js

253 ms

sync

sync

39 ms

adsct

adsct

96 ms

adsct

adsct

174 ms

sync

sync

31 ms

tap.php

tap.php

35 ms

ip.json

ip.json

86 ms

rum

rum

21 ms

log

log

19 ms

pd.js

pd.js

17 ms

Accessibility Review

graebel.com accessibility score

77

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

button, link, and menuitem elements do not have accessible names.

High

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

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

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

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

graebel.com 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

Missing source maps for large first-party JavaScript

SEO Factors

graebel.com SEO score

99

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

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 Graebel.com 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 Graebel.com 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

graebel.com

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