Tools & Wizards About Us
translator.imtranslator.net screenshot

Report Summary

  • 0

    Performance

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

translator.imtranslator.net

Free translation, ImTranslator.com

Page Load Speed

1.5 sec in total

First Response

150 ms

Resources Loaded

1.2 sec

Page Rendered

204 ms

translator.imtranslator.net screenshot

About Website

Click here to check amazing Translator Im content for China. Otherwise, check out these important facts you probably never knew about translator.imtranslator.net

Free online multilingual translation software for English, French, German, Russian and Spanish languages.

Visit translator.imtranslator.net

Key Findings

We analyzed Translator.imtranslator.net page load time and found that the first response time was 150 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 25% of websites can load faster.

Performance Metrics

translator.imtranslator.net performance score

0

Network Requests Diagram

translator.imtranslator.net

150 ms

LOADER.js

75 ms

default1.asp

139 ms

white.css

128 ms

common.js

204 ms

Our browser made a total of 60 requests to load all elements on the main page. We found that 88% of them (53 requests) were addressed to the original Translator.imtranslator.net, 5% (3 requests) were made to Google-analytics.com and 3% (2 requests) were made to C.statcounter.com. The less responsive or slowest element that took the longest time to load (306 ms) belongs to the original domain Translator.imtranslator.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 110.9 kB (63%)

Content Size

175.3 kB

After Optimization

64.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Translator.imtranslator.net main page is 175.3 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. 20% of websites need less resources to load. Javascripts take 157.8 kB which makes up the majority of the site volume.

HTML Optimization

-55%

Potential reduce by 675 B

  • Original 1.2 kB
  • After minification 1.2 kB
  • After compression 556 B

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 675 B or 55% of the original size.

Image Optimization

-24%

Potential reduce by 930 B

  • Original 3.9 kB
  • After minification 2.9 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. Obviously, Translator Im needs image optimization as it can save up to 930 B or 24% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-63%

Potential reduce by 99.0 kB

  • Original 157.8 kB
  • After minification 120.2 kB
  • After compression 58.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 99.0 kB or 63% of the original size.

CSS Optimization

-83%

Potential reduce by 10.3 kB

  • Original 12.4 kB
  • After minification 10.8 kB
  • After compression 2.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. Translator.imtranslator.net needs all CSS files to be minified and compressed as it can save up to 10.3 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 43 (73%)

Requests Now

59

After Optimization

16

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Translator Im. 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 as a result speed up the page load time.

Network Requests Diagram

translator.imtranslator.net

translator.imtranslator.net

150 ms

LOADER.js

LOADER.js

75 ms

default1.asp

default1.asp

139 ms

white.css

white.css

128 ms

common.js

common.js

204 ms

plugin.js

plugin.js

135 ms

util.js

util.js

201 ms

sha1.js

sha1.js

135 ms

google_top_exp.js

google_top_exp.js

23 ms

en-remarks.js

en-remarks.js

130 ms

common.js

common.js

258 ms

translator.js

translator.js

269 ms

toolbar.js

toolbar.js

260 ms

script.js

script.js

262 ms

tts.js

tts.js

272 ms

spellclient.js

spellclient.js

275 ms

decoder-client.js

decoder-client.js

276 ms

VirkClient.js

VirkClient.js

278 ms

toolbar.css

toolbar.css

283 ms

btn-on.gif

btn-on.gif

131 ms

empty.gif

empty.gif

132 ms

copy.gif

copy.gif

133 ms

paste.gif

paste.gif

135 ms

cut.gif

cut.gif

136 ms

delete.gif

delete.gif

156 ms

sp.gif

sp.gif

181 ms

dictionary.gif

dictionary.gif

182 ms

speller.gif

speller.gif

183 ms

decoder.gif

decoder.gif

184 ms

tts.gif

tts.gif

185 ms

print.gif

print.gif

188 ms

email.gif

email.gif

241 ms

font-b.gif

font-b.gif

242 ms

help.gif

help.gif

242 ms

arrows.jpg

arrows.jpg

242 ms

tb_bottom-bg.gif

tb_bottom-bg.gif

244 ms

tts.gif

tts.gif

247 ms

direction.gif

direction.gif

300 ms

exit-small.gif

exit-small.gif

301 ms

Im_donate-468x60.gif

Im_donate-468x60.gif

302 ms

indicator.gif

indicator.gif

302 ms

card_eng468.gif

card_eng468.gif

304 ms

attr1.png

attr1.png

306 ms

source.asp

source.asp

302 ms

empty.gif

empty.gif

288 ms

btn-on2.gif

btn-on2.gif

288 ms

tb-top-bg.gif

tb-top-bg.gif

288 ms

target.asp

target.asp

268 ms

empty.gif

empty.gif

264 ms

default.asp

default.asp

294 ms

system.css

system.css

70 ms

source.js

source.js

68 ms

net.js

net.js

70 ms

target.js

target.js

85 ms

counter.js

counter.js

15 ms

t.php

t.php

148 ms

ga.js

ga.js

31 ms

t.php

t.php

151 ms

__utm.gif

__utm.gif

15 ms

__utm.gif

__utm.gif

25 ms

Accessibility Review

translator.imtranslator.net accessibility score

68

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

<frame> or <iframe> elements do not have a title

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

translator.imtranslator.net best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

translator.imtranslator.net SEO score

75

Search Engine Optimization Advices

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 Translator.imtranslator.net 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 Translator.imtranslator.net 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

translator.imtranslator.net

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