Tools & Wizards About Us
interpreterpaul.com screenshot

Report Summary

  • 43

    Performance

    Renders faster than
    62% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

interpreterpaul.com

Paolo Cappelli | @interpreterpaul | Conference Interpreter

Page Load Speed

3.2 sec in total

First Response

368 ms

Resources Loaded

2.7 sec

Page Rendered

182 ms

interpreterpaul.com screenshot

About Website

Click here to check amazing Interpreter Paul content. Otherwise, check out these important facts you probably never knew about interpreterpaul.com

Visit interpreterpaul.com

Key Findings

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

interpreterpaul.com performance score

43

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

29/100

10%

LCP (Largest Contentful Paint)

Value10.7 s

0/100

25%

SI (Speed Index)

Value11.4 s

5/100

10%

TBT (Total Blocking Time)

Value320 ms

76/100

30%

CLS (Cumulative Layout Shift)

Value0.086

93/100

15%

TTI (Time to Interactive)

Value10.0 s

26/100

10%

Network Requests Diagram

interpreterpaul.com

368 ms

www.interpreterpaul.com

727 ms

analytics.js

27 ms

shareaholic.js

65 ms

all.min.css

180 ms

Our browser made a total of 89 requests to load all elements on the main page. We found that 27% of them (24 requests) were addressed to the original Interpreterpaul.com, 64% (57 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (967 ms) relates to the external source Interpretetraduttore.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 182.9 kB (35%)

Content Size

515.4 kB

After Optimization

332.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Interpreterpaul.com main page is 515.4 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. Only a small number of websites need less resources to load. HTML takes 208.9 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 177.2 kB

  • Original 208.9 kB
  • After minification 206.3 kB
  • After compression 31.7 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 177.2 kB or 85% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 58.8 kB
  • After minification 58.8 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 Paul images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 1.7 kB

  • Original 191.6 kB
  • After minification 191.6 kB
  • After compression 189.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. This website has mostly compressed JavaScripts.

CSS Optimization

-7%

Potential reduce by 4.0 kB

  • Original 56.1 kB
  • After minification 56.1 kB
  • After compression 52.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. Interpreterpaul.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 24 (83%)

Requests Now

29

After Optimization

5

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

interpreterpaul.com

interpreterpaul.com

368 ms

www.interpreterpaul.com

www.interpreterpaul.com

727 ms

analytics.js

analytics.js

27 ms

shareaholic.js

shareaholic.js

65 ms

all.min.css

all.min.css

180 ms

bootstrap.min.css

bootstrap.min.css

308 ms

front.css

front.css

375 ms

jquery.min.js

jquery.min.js

536 ms

jquery-migrate.min.js

jquery-migrate.min.js

416 ms

popper.min.js

popper.min.js

429 ms

bootstrap.min.js

bootstrap.min.js

602 ms

front.js

front.js

430 ms

js

js

111 ms

css

css

55 ms

css

css

71 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

517 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

569 ms

wp-polyfill.min.js

wp-polyfill.min.js

575 ms

hooks.min.js

hooks.min.js

572 ms

i18n.min.js

i18n.min.js

677 ms

jquery.form.min.js

jquery.form.min.js

677 ms

hcaptcha-divi.min.js

hcaptcha-divi.min.js

752 ms

scripts.min.js

scripts.min.js

852 ms

smoothscroll.js

smoothscroll.js

754 ms

jquery.mobile.js

jquery.mobile.js

785 ms

common.js

common.js

839 ms

collect

collect

16 ms

js

js

103 ms

Paolo-Cappelli-1080x607.jpg

Paolo-Cappelli-1080x607.jpg

967 ms

Logo-Paolo-Cappelli-con-testoEN.svg

Logo-Paolo-Cappelli-con-testoEN.svg

217 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoooCM.woff

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoooCM.woff

52 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoooCP.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoooCP.ttf

54 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaooCM.woff

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaooCM.woff

46 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaooCP.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaooCP.ttf

53 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEooCM.woff

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEooCM.woff

53 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEooCP.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEooCP.ttf

54 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaooCM.woff

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaooCM.woff

72 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaooCP.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaooCP.ttf

75 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao4CM.woff

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao4CM.woff

74 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao4CP.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao4CP.ttf

71 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpYCM.woff

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpYCM.woff

72 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpYCP.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpYCP.ttf

75 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pYCM.woff

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pYCM.woff

79 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pYCP.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pYCP.ttf

79 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapYCM.woff

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapYCM.woff

78 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapYCP.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapYCP.ttf

76 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpYCM.woff

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpYCM.woff

79 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpYCP.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpYCP.ttf

78 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vAkw.woff

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vAkw.woff

99 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vAkA.ttf

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vAkA.ttf

102 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3iu4nAkw.woff

6xKydSBYKcSV-LCoeQqfX1RYOo3iu4nAkw.woff

99 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3iu4nAkA.ttf

6xKydSBYKcSV-LCoeQqfX1RYOo3iu4nAkA.ttf

101 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3i54rAkw.woff

6xKydSBYKcSV-LCoeQqfX1RYOo3i54rAkw.woff

99 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3i54rAkA.ttf

6xKydSBYKcSV-LCoeQqfX1RYOo3i54rAkA.ttf

100 ms

6xK3dSBYKcSV-LCoeQqfX1RYOo3aPA.woff

6xK3dSBYKcSV-LCoeQqfX1RYOo3aPA.woff

102 ms

6xK3dSBYKcSV-LCoeQqfX1RYOo3aPw.ttf

6xK3dSBYKcSV-LCoeQqfX1RYOo3aPw.ttf

103 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zAkw.woff

6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zAkw.woff

103 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zAkA.ttf

6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zAkA.ttf

103 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3i94_Akw.woff

6xKydSBYKcSV-LCoeQqfX1RYOo3i94_Akw.woff

105 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3i94_AkA.ttf

6xKydSBYKcSV-LCoeQqfX1RYOo3i94_AkA.ttf

104 ms

modules.woff

modules.woff

437 ms

1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4VrMPrc.woff

1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4VrMPrc.woff

104 ms

1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4VrMPrQ.ttf

1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4VrMPrQ.ttf

104 ms

1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4WjMPrc.woff

1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4WjMPrc.woff

105 ms

1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4WjMPrQ.ttf

1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4WjMPrQ.ttf

107 ms

1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4TbMPrc.woff

1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4TbMPrc.woff

107 ms

1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4TbMPrQ.ttf

1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4TbMPrQ.ttf

106 ms

1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4ejMPrc.woff

1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4ejMPrc.woff

59 ms

1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4ejMPrQ.ttf

1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4ejMPrQ.ttf

60 ms

1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4WjNPrc.woff

1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4WjNPrc.woff

61 ms

1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4WjNPrQ.ttf

1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4WjNPrQ.ttf

62 ms

1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4bbLPrc.woff

1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4bbLPrc.woff

61 ms

1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4bbLPrQ.ttf

1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4bbLPrQ.ttf

45 ms

1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4Y_LPrc.woff

1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4Y_LPrc.woff

42 ms

1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4Y_LPrQ.ttf

1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4Y_LPrQ.ttf

44 ms

1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4ejLPrc.woff

1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4ejLPrc.woff

84 ms

1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4ejLPrQ.ttf

1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4ejLPrQ.ttf

85 ms

1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4cHLPrc.woff

1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4cHLPrc.woff

84 ms

1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4cHLPrQ.ttf

1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4cHLPrQ.ttf

84 ms

style.min.css

style.min.css

143 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCIPrQ.ttf

11 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf

9 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrQ.ttf

3 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaorCIPrQ.ttf

10 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao7CIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao7CIPrQ.ttf

10 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCIPrQ.ttf

10 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrQ.ttf

25 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCIPrQ.ttf

24 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCIPrQ.ttf

24 ms

Accessibility Review

interpreterpaul.com accessibility score

90

Accessibility Issues

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

interpreterpaul.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

Page has valid source maps

SEO Factors

interpreterpaul.com SEO score

86

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

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 Interpreterpaul.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 Interpreterpaul.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

interpreterpaul.com

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