Tools & Wizards About Us
ingressivespeech.info screenshot

Report Summary

  • 0

    Performance

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 67

    SEO

    Google-friendlier than
    25% of websites

ingressivespeech.info

Robert Eklund's Ingressive Phonation and Speech Page

Page Load Speed

3.1 sec in total

First Response

235 ms

Resources Loaded

2.3 sec

Page Rendered

527 ms

ingressivespeech.info screenshot

About Website

Visit ingressivespeech.info now to see the best up-to-date Ingressive Speech content and also check out these interesting facts you probably never knew about ingressivespeech.info

Robert Eklund's page devoted to pulmonic ingressive phonation/speech, i.e. sounds produced on pulmonic (lung) airstream.

Visit ingressivespeech.info

Key Findings

We analyzed Ingressivespeech.info page load time and found that the first response time was 235 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

ingressivespeech.info performance score

0

Network Requests Diagram

ingressivespeech.info

235 ms

LinguisticsIngressive.htm

454 ms

LinguisticsIngressive.htm

470 ms

LinguisticsIngressive.htm

125 ms

style.css

114 ms

Our browser made a total of 29 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Ingressivespeech.info, 97% (28 requests) were made to Ida.liu.se. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Ida.liu.se.

Page Optimization Overview & Recommendations

Page size can be reduced by 36.4 kB (4%)

Content Size

943.7 kB

After Optimization

907.4 kB

  • HTML
  • Images
  • CSS

In fact, the total size of Ingressivespeech.info main page is 943.7 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. 30% of websites need less resources to load. Images take 942.2 kB which makes up the majority of the site volume.

HTML Optimization

-51%

Potential reduce by 520 B

  • Original 1.0 kB
  • After minification 1.0 kB
  • After compression 493 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 520 B or 51% of the original size.

Image Optimization

-4%

Potential reduce by 35.8 kB

  • Original 942.2 kB
  • After minification 906.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. Ingressive Speech images are well optimized though.

CSS Optimization

-15%

Potential reduce by 83 B

  • Original 563 B
  • After minification 563 B
  • After compression 480 B

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. Ingressivespeech.info needs all CSS files to be minified and compressed as it can save up to 83 B or 15% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

26

After Optimization

26

  • AJAX
  • Images
  • CSS

The browser has sent 26 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ingressive Speech. According to our analytics all requests are already optimized.

Network Requests Diagram

ingressivespeech.info

ingressivespeech.info

235 ms

LinguisticsIngressive.htm

LinguisticsIngressive.htm

454 ms

LinguisticsIngressive.htm

LinguisticsIngressive.htm

470 ms

LinguisticsIngressive.htm

LinguisticsIngressive.htm

125 ms

style.css

style.css

114 ms

ingressive-purring_cheetah_spectrogram.jpg

ingressive-purring_cheetah_spectrogram.jpg

337 ms

ingressive-IngressiveSpeech_Distribution_600x300.jpg

ingressive-IngressiveSpeech_Distribution_600x300.jpg

675 ms

ingressive-nonlinguistic-sounds.jpg

ingressive-nonlinguistic-sounds.jpg

451 ms

ingressive-linguistic-sounds.jpg

ingressive-linguistic-sounds.jpg

452 ms

ingressive-words.jpg

ingressive-words.jpg

452 ms

ingressive-phrases.jpg

ingressive-phrases.jpg

452 ms

ingressive-areas.jpg

ingressive-areas.jpg

448 ms

ingressive-unclear-regions.jpg

ingressive-unclear-regions.jpg

560 ms

ingressive-Eklund_JIPA_2008_Fig_1a_egr_ja_male_th.jpg

ingressive-Eklund_JIPA_2008_Fig_1a_egr_ja_male_th.jpg

674 ms

ingressive-Eklund_JIPA_2008_Fig_1b_ingr_ja_male_th.jpg

ingressive-Eklund_JIPA_2008_Fig_1b_ingr_ja_male_th.jpg

671 ms

ingressive-Eklund_JIPA_2008_Fig_2a_egr_ja_male_th.jpg

ingressive-Eklund_JIPA_2008_Fig_2a_egr_ja_male_th.jpg

672 ms

ingressive-Eklund_JIPA_2008_Fig_2b_ingr_ja_male_th.jpg

ingressive-Eklund_JIPA_2008_Fig_2b_ingr_ja_male_th.jpg

673 ms

ingressive-Eklund_JIPA_2008_Fig_3_egr-ingr_mm_female_th.jpg

ingressive-Eklund_JIPA_2008_Fig_3_egr-ingr_mm_female_th.jpg

668 ms

ingressive-Eklund_JIPA_2008_Fig_4_egr-ingr_nej_female_th.jpg

ingressive-Eklund_JIPA_2008_Fig_4_egr-ingr_nej_female_th.jpg

782 ms

ingressive-Eklund_JIPA_2008_Fig_5a_egr_ja-gor-det_child-male_th.jpg

ingressive-Eklund_JIPA_2008_Fig_5a_egr_ja-gor-det_child-male_th.jpg

783 ms

ingressive-Eklund_JIPA_2008_Fig_5b_ingr_mm-gor-det_child-male_th.jpg

ingressive-Eklund_JIPA_2008_Fig_5b_ingr_mm-gor-det_child-male_th.jpg

783 ms

ingressive-Eklund_JIPA_2008_Fig_6_ingr_eh-eg-veit-ikki_female_th.jpg

ingressive-Eklund_JIPA_2008_Fig_6_ingr_eh-eg-veit-ikki_female_th.jpg

783 ms

ingressive-Eklund_JIPA_2008_Fig_7a_ingr-aye_egr-aye-it-wasn-a-bad_female_th.jpg

ingressive-Eklund_JIPA_2008_Fig_7a_ingr-aye_egr-aye-it-wasn-a-bad_female_th.jpg

786 ms

ingressive-Eklund_JIPA_2008_Fig_7b_ingr-aye_egr-aye-i-ken_male_th.jpg

ingressive-Eklund_JIPA_2008_Fig_7b_ingr-aye_egr-aye-i-ken_male_th.jpg

785 ms

ingressive-annika_01_tn.jpg

ingressive-annika_01_tn.jpg

895 ms

ingressive-annika_02_tn.jpg

ingressive-annika_02_tn.jpg

894 ms

ingressive-leopard_th.jpg

ingressive-leopard_th.jpg

1006 ms

RobertEklunds_Homepage_Footer_ON.png

RobertEklunds_Homepage_Footer_ON.png

786 ms

RobertEklunds_Homepage_Footer_OFF.png

RobertEklunds_Homepage_Footer_OFF.png

787 ms

Accessibility Review

ingressivespeech.info accessibility score

100

Accessibility Issues

Best Practices

ingressivespeech.info 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

ingressivespeech.info SEO score

67

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

robots.txt is not valid

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 Ingressivespeech.info 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 Ingressivespeech.info 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

ingressivespeech.info

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