Tools & Wizards About Us
interpreter.services screenshot

Report Summary

  • 23

    Performance

    Renders faster than
    42% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 78% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

interpreter.services

Home | GLOBO

Page Load Speed

1.4 sec in total

First Response

29 ms

Resources Loaded

834 ms

Page Rendered

565 ms

interpreter.services screenshot

About Website

Welcome to interpreter.services homepage info - get ready to check Interpreter best content right away, or after learning these important things about interpreter.services

GLOBO combines innovative technology, qualified linguists and actionable data insights to deliver the highest-quality translation and interpreting services.

Visit interpreter.services

Key Findings

We analyzed Interpreter.services page load time and found that the first response time was 29 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

interpreter.services performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

43/100

10%

LCP (Largest Contentful Paint)

Value9.8 s

0/100

25%

SI (Speed Index)

Value7.1 s

31/100

10%

TBT (Total Blocking Time)

Value4,130 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.014

100/100

15%

TTI (Time to Interactive)

Value19.7 s

2/100

10%

Network Requests Diagram

interpreter.services

29 ms

www.helloglobo.com

114 ms

jquery-1.7.1.js

31 ms

main.min.css

64 ms

theme-overrides.min.css

44 ms

Our browser made a total of 162 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Interpreter.services, 59% (95 requests) were made to Globo.report-uri.com and 26% (42 requests) were made to Helloglobo.com. The less responsive or slowest element that took the longest time to load (496 ms) relates to the external source Helloglobo.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 255.0 kB (17%)

Content Size

1.5 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Interpreter.services main page is 1.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. 75% 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 980.5 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 241.9 kB

  • Original 329.7 kB
  • After minification 301.1 kB
  • After compression 87.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 241.9 kB or 73% of the original size.

Image Optimization

-0%

Potential reduce by 6 B

  • Original 980.5 kB
  • After minification 980.4 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. Interpreter images are well optimized though.

JavaScript Optimization

-5%

Potential reduce by 6.3 kB

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

-20%

Potential reduce by 6.7 kB

  • Original 33.3 kB
  • After minification 33.3 kB
  • After compression 26.5 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. Interpreter.services needs all CSS files to be minified and compressed as it can save up to 6.7 kB or 20% of the original size.

Requests Breakdown

Number of requests can be reduced by 30 (52%)

Requests Now

58

After Optimization

28

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

interpreter.services

interpreter.services

29 ms

www.helloglobo.com

www.helloglobo.com

114 ms

jquery-1.7.1.js

jquery-1.7.1.js

31 ms

main.min.css

main.min.css

64 ms

theme-overrides.min.css

theme-overrides.min.css

44 ms

Style.min.css

Style.min.css

48 ms

module_75574702393_Header.min.css

module_75574702393_Header.min.css

77 ms

module_75729603358_Banner_Section.min.css

module_75729603358_Banner_Section.min.css

52 ms

css

css

46 ms

css

css

66 ms

css

css

71 ms

all.min.css

all.min.css

69 ms

reportOnly

reportOnly

65 ms

theme-foundation-v1-0.min.css

theme-foundation-v1-0.min.css

63 ms

js

js

200 ms

embed.js

embed.js

48 ms

jquery.min.js

jquery.min.js

59 ms

animation_plugin.min.js

animation_plugin.min.js

61 ms

main.min.js

main.min.js

69 ms

project.js

project.js

64 ms

module_75574702393_Header.min.js

module_75574702393_Header.min.js

68 ms

loader.js

loader.js

61 ms

437614.js

437614.js

195 ms

index.js

index.js

195 ms

reportOnly

reportOnly

158 ms

reportOnly

reportOnly

156 ms

reportOnly

reportOnly

37 ms

reportOnly

reportOnly

164 ms

reportOnly

reportOnly

156 ms

reportOnly

reportOnly

155 ms

css2

css2

28 ms

font-awesome.css

font-awesome.css

21 ms

reportOnly

reportOnly

177 ms

reportOnly

reportOnly

178 ms

gtm.js

gtm.js

187 ms

reportOnly

reportOnly

172 ms

reportOnly

reportOnly

171 ms

reportOnly

reportOnly

171 ms

reportOnly

reportOnly

167 ms

fbevents.js

fbevents.js

209 ms

reportOnly

reportOnly

255 ms

reportOnly

reportOnly

212 ms

reportOnly

reportOnly

211 ms

reportOnly

reportOnly

211 ms

reportOnly

reportOnly

252 ms

reportOnly

reportOnly

253 ms

reportOnly

reportOnly

287 ms

reportOnly

reportOnly

286 ms

reportOnly

reportOnly

284 ms

reportOnly

reportOnly

282 ms

reportOnly

reportOnly

283 ms

reportOnly

reportOnly

284 ms

reportOnly

reportOnly

289 ms

reportOnly

reportOnly

292 ms

reportOnly

reportOnly

291 ms

reportOnly

reportOnly

291 ms

reportOnly

reportOnly

291 ms

reportOnly

reportOnly

293 ms

reportOnly

reportOnly

316 ms

reportOnly

reportOnly

320 ms

reportOnly

reportOnly

314 ms

reportOnly

reportOnly

316 ms

reportOnly

reportOnly

316 ms

reportOnly

reportOnly

317 ms

reportOnly

reportOnly

320 ms

reportOnly

reportOnly

320 ms

reportOnly

reportOnly

321 ms

reportOnly

reportOnly

321 ms

reportOnly

reportOnly

324 ms

reportOnly

reportOnly

322 ms

reportOnly

reportOnly

323 ms

reportOnly

reportOnly

328 ms

reportOnly

reportOnly

326 ms

reportOnly

reportOnly

329 ms

reportOnly

reportOnly

338 ms

reportOnly

reportOnly

337 ms

reportOnly

reportOnly

338 ms

reportOnly

reportOnly

347 ms

reportOnly

reportOnly

338 ms

reportOnly

reportOnly

346 ms

reportOnly

reportOnly

348 ms

reportOnly

reportOnly

347 ms

reportOnly

reportOnly

346 ms

reportOnly

reportOnly

348 ms

reportOnly

reportOnly

351 ms

reportOnly

reportOnly

352 ms

reportOnly

reportOnly

351 ms

reportOnly

reportOnly

365 ms

reportOnly

reportOnly

356 ms

reportOnly

reportOnly

355 ms

reportOnly

reportOnly

357 ms

reportOnly

reportOnly

362 ms

reportOnly

reportOnly

369 ms

reportOnly

reportOnly

368 ms

reportOnly

reportOnly

364 ms

reportOnly

reportOnly

364 ms

reportOnly

reportOnly

371 ms

reportOnly

reportOnly

372 ms

reportOnly

reportOnly

372 ms

reportOnly

reportOnly

375 ms

reportOnly

reportOnly

373 ms

reportOnly

reportOnly

377 ms

reportOnly

reportOnly

375 ms

reportOnly

reportOnly

385 ms

reportOnly

reportOnly

383 ms

reportOnly

reportOnly

382 ms

reportOnly

reportOnly

393 ms

reportOnly

reportOnly

380 ms

reportOnly

reportOnly

396 ms

reportOnly

reportOnly

391 ms

reportOnly

reportOnly

390 ms

reportOnly

reportOnly

395 ms

reportOnly

reportOnly

393 ms

reportOnly

reportOnly

396 ms

reportOnly

reportOnly

403 ms

reportOnly

reportOnly

345 ms

reportOnly

reportOnly

344 ms

reportOnly

reportOnly

342 ms

GLOBO-Logo-1.svg

GLOBO-Logo-1.svg

80 ms

arrow.svg

arrow.svg

75 ms

Video-icon.svg

Video-icon.svg

76 ms

Better-Outcomes-Small.png

Better-Outcomes-Small.png

80 ms

Frame%20342.svg

Frame%20342.svg

76 ms

globo-home-chat.png

globo-home-chat.png

457 ms

Arrow_10-1.svg

Arrow_10-1.svg

164 ms

Manage-Icon.svg

Manage-Icon.svg

112 ms

arrow-long.svg

arrow-long.svg

163 ms

Access-Icon.svg

Access-Icon.svg

115 ms

GLOBO-Features.png

GLOBO-Features.png

187 ms

Interpreting-Icon.svg

Interpreting-Icon.svg

166 ms

Translation-Icon.svg

Translation-Icon.svg

188 ms

Integrations-Icon.svg

Integrations-Icon.svg

186 ms

Arrow_10%20(1).svg

Arrow_10%20(1).svg

188 ms

BKG%20Shape.svg

BKG%20Shape.svg

189 ms

Why-GLOBO.png

Why-GLOBO.png

225 ms

Betsy%20Payne%20-%20final.png

Betsy%20Payne%20-%20final.png

231 ms

Jessica%20Schiminske%20-%20Employee%20Spotlight.png

Jessica%20Schiminske%20-%20Employee%20Spotlight.png

229 ms

Wellness%20Month%20Blog%20Feature%20Image.png

Wellness%20Month%20Blog%20Feature%20Image.png

224 ms

Make-World-Better-Icon.svg

Make-World-Better-Icon.svg

225 ms

GLOBO-Logo_White.png

GLOBO-Logo_White.png

234 ms

Orion%20Badges%20Dark-9001%20WHT.png

Orion%20Badges%20Dark-9001%20WHT.png

233 ms

Orion%20Badges%20Dark-17100%20WHT.png

Orion%20Badges%20Dark-17100%20WHT.png

234 ms

font

font

112 ms

font

font

162 ms

greycliffcf-medium-webfont.woff

greycliffcf-medium-webfont.woff

432 ms

greycliffcf-regular-webfont.woff

greycliffcf-regular-webfont.woff

489 ms

greycliffcf-light-webfont.woff

greycliffcf-light-webfont.woff

496 ms

greycliffcf-bold-webfont.woff

greycliffcf-bold-webfont.woff

463 ms

greycliffcf-heavy-webfont.woff

greycliffcf-heavy-webfont.woff

249 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

72 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

59 ms

reportOnly

reportOnly

325 ms

reportOnly

reportOnly

321 ms

reportOnly

reportOnly

315 ms

reportOnly

reportOnly

320 ms

feedbackweb-new.js

feedbackweb-new.js

186 ms

437614.js

437614.js

162 ms

leadflows.js

leadflows.js

167 ms

conversations-embed.js

conversations-embed.js

160 ms

fb.js

fb.js

158 ms

web-interactives-embed.js

web-interactives-embed.js

148 ms

437614.js

437614.js

184 ms

Accessibility Review

interpreter.services accessibility score

92

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

[id] attributes on active, focusable elements are not unique

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

interpreter.services best practices score

75

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

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

interpreter.services SEO score

86

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

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

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 Interpreter.services 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 Interpreter.services 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

interpreter.services

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