Translations.Ca - Info receives about n/a unique visitors and n/a page views per day which should earn about n/a/day from advertising revenue. Estimated site value is n/a. According to Alexa Traffic Rank is ranked number 0 in the world and 0% of global Internet users visit it. Site is hosted in United States and links to network IP address This server supports HTTPS and doesn't support HTTP/2.

About -

Technologies used on Website

UI frameworks
JavaScript Libraries
jQuery Migrate
Programming Languages
PHP Profile

Title: Translations.CA | in FRENCH only inc. & in SPANISH, too! - Home
Description: Canadian commercial translation agency for French, Spanish and English. Toronto, Ontario.
Certified Translation Services | Canadian French English Spanish Specialists Toronto Ontario
Keywords: Translations in English, French Canadian, Quebecois & Spanish languages and all major languages. Working with businesses in fields like CPG food, cosmetics, cannabis. Toronto, Ontario translation traduction traduccion business B2B
Last update was 244 days ago
This can take up to 60 seconds. Please wait...

* is not linking to, promoting or affiliated with in any way. Only publicly available statistics data are displayed.

How popular is

Is this your site?
Verify your site's metrics.
Daily Unique Visitors:
Monthly Unique Visitors:
Pages per Visit:
Daily Pageviews:
Alexa Rank:
Currently Not Available visit alexa
Alexa Reach:
n/a   (of global internet users)
Avg. visit duration:
Bounce rate:
*All traffic values are estimates only.

Alexa Traffic Ranks
Search Traffic

Visitors by country

Currently Not Available

Where do visitors go on this site?

Currently Not Available

Competitive Data

(Rank based on keywords, cost and organic traffic)
Organic Keywords:
(Number of keywords in top 20 Google SERP)
Organic Traffic:
(Number of visitors coming from top 20 search results)
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
Adwords Keywords:
(Keywords a website is buying in Google AdWords for ads that appear in paid search results)
Adwords Traffic:
(Number of visitors brought to the website via paid search results)
Adwords Cost:
(Estimated budget spent for buying keywords in Google AdWords for ads that appear in paid search results - monthly estimation)

+ Moz Data

Domain Authority:
Page Authority:

+ How socially engaged is

Google +:

+ Ad Experience Report

Summary of the ad experience rating of a site for a specific platform.

Desktop summary

Root domain:
(The Ad Standard region to which this site has been assigned.)
Ad filtering:
(Chrome is not filtering ads on your site.)
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed

Mobile summary

(The Ad Standard region to which this site has been assigned.)
Ad filtering:
(Chrome is not filtering ads on your site.)
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed

+ Abusive Experience Report

Root domain:
(Chrome is not preventing your site from opening new windows or tabs.)
(The status of the site reviewed for the abusive experiences.)
Not reviewed

+ How much can earn?

Daily Revenue:
Monthly Revenue:
Yearly Revenue:
*All earnings values are estimates only.

Daily earning by country

Currently Not Available

How much money do lose due to Adblock?

Daily Revenue Loss:
Monthly Revenue Loss:
Yearly Revenue Loss:
Daily Pageviews Blocked:
Monthly Pageviews Blocked:
Yearly Pageviews Blocked:
*All earnings values are estimates only.

Daily revenue loss by country

Currently Not Available

How much is worth?

Website Value:

+ Where is hosted?

Server IP:
Server Location:

United States, US

Other sites hosted on

There are no other sites hosted on this IP

+ How fast does load?

Average Load Time:
n/a ms n/a % of sites are slower

Page Speed (Google PageSpeed Insights) - Desktop

Currently Not Available

Page Speed (Google PageSpeed Insights) - Mobile

0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.

Origin Data

All pages served from this origin have an speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.

Lab Data

Speed Index 10.0 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 9.0 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
First Contentful Paint 8.4 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.
First Meaningful Paint 9.0 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 90 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more.
Time to Interactive 9.2 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Third-Party Usage
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more.
First Contentful Paint (3G) 17798 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn more.
Total Blocking Time 30 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Estimated Input Latency 10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

JavaScript execution time - 0.9 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

Total CPU TimeScript EvaluationScript Parse
846 ms139 ms4 ms
827 ms537 ms10 ms
186 ms132 ms11 ms
125 ms104 ms8 ms
Remove unused CSS - Potential savings of 637 KB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.

SizePotential Savings
558 KB545 KB
91 KB91 KB
Avoids enormous network payloads - Total size was 1,191 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

558 KB
130 KB
109 KB
95 KB
91 KB
63 KB
35 KB
23 KB
22 KB
18 KB
Minimize main-thread work - 2.1 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this.

Time Spent
Script Evaluation
966 ms
415 ms
Style & Layout
378 ms
Parse HTML & CSS
169 ms
75 ms
Script Parsing & Compilation
55 ms
Garbage Collection
2 ms
Serve images in next-gen formats - Potential savings of 22 KB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.

SizePotential Savings
23 KB13 KB
18 KB9 KB
Avoids an excessive DOM size - 266 elements
Browser engineers recommend pages contain fewer than ~1,500 DOM elements. The sweet spot is a tree depth < 32 elements and fewer than 60 children/parent element. A large DOM can increase memory usage, cause longer [style calculations](, and produce costly [layout reflows]( Learn more.

Total DOM Elements
Maximum DOM Depth
Maximum Child Elements
Minify JavaScript - Potential savings of 12 KB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

SizePotential Savings
35 KB12 KB
Avoid multiple page redirects - Potential savings of 630 ms
Redirects introduce additional delays before the page can be loaded. Learn more.

Time Spent
Keep request counts low and transfer sizes small - 24 requests • 5,240 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
245240 KB
14049 KB
2649 KB
9461 KB
943 KB
122 KB
115 KB
10 KB
736 KB
Eliminate render-blocking resources - Potential savings of 7,100 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

SizePotential Savings
558 KB6630
91 KB3480
130 KB4230
63 KB2580
2 KB480
95 KB3630
0 KB180
10 KB480
109 KB3180
17 KB630
Enable text compression - Potential savings of 898 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

SizePotential Savings
557 KB487 KB
130 KB89 KB
109 KB80 KB
91 KB74 KB
94 KB61 KB
63 KB45 KB
35 KB27 KB
22 KB17 KB
16 KB11 KB
10 KB6 KB
Network Requests
Lists the network requests that were made during page load.

Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
0 ms231 ms0 KB0 KB301text/html
232 ms2194 ms22 KB22 KB200text/htmlDocument
2224 ms2729 ms558 KB557 KB200text/cssStylesheet
2224 ms2538 ms91 KB91 KB200text/cssStylesheet
2224 ms2803 ms130 KB130 KB200application/javascriptScript
2225 ms2336 ms63 KB63 KB200application/javascriptScript
2225 ms2516 ms2 KB2 KB200application/javascriptScript
2225 ms2646 ms95 KB94 KB200application/javascriptScript
2225 ms2376 ms0 KB0 KB200application/javascriptScript
2226 ms2616 ms10 KB10 KB200application/javascriptScript
2226 ms2882 ms109 KB109 KB200application/javascriptScript
2226 ms2686 ms17 KB16 KB200application/javascriptScript
2226 ms2720 ms18 KB18 KB200image/pngImage
2226 ms2722 ms23 KB23 KB200image/pngImage
2721 ms2817 ms35 KB35 KB200text/javascriptScript
2944 ms3028 ms15 KB15 KB200application/octet-streamFont
2967 ms3089 ms1 KB1 KB200image/pngImage
3007 ms3007 ms0 KB2 KB200image/pngImage
3007 ms3007 ms0 KB1 KB200image/pngImage
3086 ms3086 ms0 KB0 KB200image/svg+xmlImage
3088 ms3088 ms0 KB0 KB200image/svg+xmlImage
3090 ms3090 ms0 KB0 KB200image/svg+xmlImage
3139 ms3532 ms4049 KB3072 KB206video/mp4Media
3185 ms3226 ms1 KB0 KB200image/gifImage
Serve static assets with an efficient cache policy - 16 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

Cache TTLSize
0 ms4049 KB
0 ms558 KB
0 ms130 KB
0 ms109 KB
0 ms95 KB
0 ms91 KB
0 ms63 KB
0 ms35 KB
0 ms23 KB
0 ms18 KB
0 ms17 KB
0 ms15 KB
0 ms10 KB
0 ms2 KB
0 ms1 KB
0 ms0 KB
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
2229 ms
15 ms
2246 ms
5 ms
2563 ms
5 ms
2755 ms
20 ms
2835 ms
23 ms
2868 ms
26 ms
2911 ms
26 ms
2936 ms
23 ms
2960 ms
12 ms
2972 ms
17 ms
2989 ms
17 ms
3006 ms
110 ms
3117 ms
23 ms
3140 ms
24 ms
3171 ms
27 ms
3198 ms
28 ms
3227 ms
6 ms
Ensure text remains visible during webfont load
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

Potential Savings
84 ms
Preconnect to required origins
Consider adding preconnect or dns-prefetch resource hints to establish early connections to important third-party origins. Learn more.

Minify CSS
Minifying CSS files can reduce network payload sizes. Learn more.

Server Backend Latencies - 0 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn more.

Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

Minimize Critical Requests Depth - 12 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.

Preload key requests
Consider using to prioritize fetching resources that are currently requested later in page load. Learn more.

User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.

Use video formats for animated content
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more.

Reduce server response times (TTFB) - Root document took 1,960 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

Efficiently encode images
Optimized images load faster and consume less cellular data. Learn more.

Network Round Trip Times - 0 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn more.

Page Speed (Google PageSpeed Insights) - v2

Suggestions Summary

Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 898.1KiB (79% reduction).

Compressing could save 486.5KiB (87% reduction).
Compressing could save 89.3KiB (68% reduction).
Compressing could save 80.2KiB (73% reduction).
Compressing could save 74KiB (81% reduction).
Compressing could save 61.4KiB (65% reduction).
Compressing could save 45.5KiB (72% reduction).
Compressing could save 26.8KiB (76% reduction).
Compressing could save 16.7KiB (76% reduction).
Compressing could save 11KiB (66% reduction).
Compressing could save 5.9KiB (60% reduction).
Compressing could save 894B (51% reduction).

Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 8 blocking script resources and 2 blocking CSS resources. This causes a delay in rendering your page.

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.Remove render-blocking JavaScript:
Optimize CSS Delivery of the following:

Reduce server response time

In our test, your server responded in 1.9 seconds.

There are many factors that can slow down your server response time. Please read our recommendations to learn how you can monitor and measure where your server is spending the most time.

Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources: (expiration not specified) (expiration not specified) (expiration not specified) (expiration not specified) (expiration not specified) (expiration not specified) (expiration not specified) (expiration not specified)

Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and *** time.

Minify JavaScript for the following resources to reduce their size by 12KiB (35% reduction).

Minifying could save 12KiB (35% reduction).

Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 5.2KiB (13% reduction).

Compressing could save 3.1KiB (14% reduction).
Compressing could save 2.1KiB (12% reduction).

Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and p*** times.

Minify HTML for the following resources to reduce their size by 5.1KiB (24% reduction).

Minifying could save 5.1KiB (24% reduction).
Avoid landing page redirects
Your page has no redirects. Learn more about avoiding landing page redirects.
Avoid plugins
Your page does not appear to use plugins, which would prevent content from being usable on many platforms. Learn more about the importance of avoiding plugins.
Configure the viewport
Your page specifies a viewport matching the device's size, which allows it to render properly on all devices. Learn more about configuring viewports.
Minify CSS
Your CSS is minified. Learn more about minifying CSS.
Prioritize visible content
You have the above-the-fold content properly prioritized. Learn more about prioritizing visible content.
Size content to viewport
The contents of your page fit within the viewport. Learn more about sizing content to the viewport.
Size tap targets appropriately
All of your page's links/buttons are large enough for a user to easily tap on a touchscreen. Learn more about sizing tap targets appropriately.
Use legible font sizes
The text on your page is legible. Learn more about using legible font sizes.
Download optimized image, JavaScript, and CSS resources for this page.

+ Does use compression? does not use compression.
Original size: 21.75 KB
Compressed size: n/a
File reduced by: n/a

+ Google Safe Browsing

This site is not currently listed as suspicious Reputation Ratings

Vendor reliability:
Child safety:

+ SSL Checker - SSL Certificate Verify supports HTTPS
Verifying SSL Support. Please wait...
Common Name:
Issuer: Sectigo RSA Domain Validation Secure Server CA
Valid from: Apr 24 00:00:00 2019 GMT
Valid until: Apr 23 23:59:59 2021 GMT
Authority: Is not a CA
Common Name: Sectigo RSA Domain Validation Secure Server CA
Organization: Sectigo Limited
Location: Salford, Greater Manchester, GB
Issuer: USERTrust RSA Certification Authority
Valid from: Nov 2 00:00:00 2018 GMT
Valid until: Dec 31 23:59:59 2030 GMT
Authority: Is a CA
Keysize: 2048 Bits

+ Verify HTTP/2 Support does not support HTTP/2
Verifying HTTP/2.0 Support. Please wait...

+ Site Categories (dmoz)

North America/Canada
Business and Economy/Translation

+ Http Header

Date: Fri, 04 Oct 2019 07:10:03 GMT
Server: Apache
X-Content-Type-Options: nosniff
Content-Length: 236
Content-Type: text/html; charset=iso-8859-1

HTTP/1.1 200 OK
Date: Fri, 04 Oct 2019 07:10:05 GMT
Content-Type: text/html; charset=utf-8
Transfer-Encoding: chunked
Connection: keep-alive
X-Content-Type-Options: nosniff
Set-Cookie: ec3cb18dd5f661527d370c485ccf31fc=9b07d18ceeb1db38b6d45e1e6de88e6c; path=/; secure; HttpOnly
Expires: Wed, 17 Aug 2005 00:00:00 GMT
Last-Modified: Fri, 04 Oct 2019 07:10:05 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache

+ DNS Lookup

Currently Not Available

+ Whois Lookup

Domain Created:
Domain Age:
19 years 12 days  

whois lookup at
Domain Name:
Registry Domain ID: D755-CIRA
Registrar WHOIS Server:
Registrar URL:
Updated Date: 2019-02-18T05:12:20Z
Creation Date: 2000-09-22T01:25:16Z
Registry Expiry Date: 2020-03-19T04:00:00Z
Registrar: Co.
Registrar IANA ID:
Registrar Abuse Contact Email:
Registrar Abuse Contact Phone:
Domain Status: clientTransferProhibited
Domain Status: clientUpdateProhibited
Registry Registrant ID: 15742191-CIRA
Registrant Name: in FRENCH only inc. o/a translationsca
Registrant Organization:
Registrant Street: 25 Rockcastle Drive
Registrant City: Toronto
Registrant State/Province: ON
Registrant Postal Code: M9R2V2
Registrant Country: CA
Registrant Phone:
Registrant Phone Ext:
Registrant Fax:
Registrant Fax Ext:
Registrant Email: email
Registry Admin ID: 2843871-CIRA
Admin Name: Kim Pines
Admin Organization: in FRENCH only inc.
Admin Street: 25 Rockcastle DR
Admin City: Toronto
Admin State/Province: ON
Admin Postal Code: M9R2V2
Admin Country: CA
Admin Phone: +1.4162485648
Admin Phone Ext:
Admin Fax: +1.4166143806
Admin Fax Ext:
Admin Email: email
Registry Tech ID: 2843872-CIRA
Tech Name: Kim Pines
Tech Organization: in FRENCH only inc.
Tech Street: 25 Rockcastle DR
Tech City: Toronto
Tech State/Province: ON
Tech Postal Code: M9R2V2
Tech Country: CA
Tech Phone: +1.4162485648
Tech Phone Ext:
Tech Fax: +1.4166143806
Tech Fax Ext:
Tech Email: email
Registry Billing ID:
Billing Name:
Billing Organization:
Billing Street:
Billing City:
Billing State/Province:
Billing Postal Code:
Billing Country:
Billing Phone:
Billing Phone Ext:
Billing Fax:
Billing Fax Ext:
Billing Email:
Name Server:
Name Server:
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form:
>>> Last update of WHOIS database: 2019-10-04T07:10:08Z <<<

For more information on Whois status codes, please visit

% Use of CIRA's WHOIS service is governed by the Terms of Use in its Legal
% Notice, available at
% (c) 2019 Canadian Internet Registration Authority, (
Last update was 244 days ago
This can take up to 60 seconds. Please wait...

* is not linking to, promoting or affiliated with in any way. Only publicly available statistics data are displayed.

Recently Analyzed Sites
40 secs
1 min
1 min
2 mins
2 mins
3 mins
3 mins
3 mins
4 mins
4 mins
We are using the world's No. 1 Marketing Tool to grow our website. Activate your FREE trial today!


Install HypeStat extension in your browser to see statistics and technologies used with one click.

Hide/Remove your site data

• Use Show/Hide ESTIMATED data form to hide (Website worth, Daily ads revenue, Daily Visits, Daily Pageviews)
• Use Show/Hide WHOIS data form to hide whois data
• Use Remove form to remove all data
• If you have any problem with REMOVE/HIDE your data just drop an email at support (at) and we will remove/hide your site data manualy.
Make custom Widget for your website
Get the code now! widget