Tools & Wizards About Us
jaw-pain.net screenshot

Report Summary

  • 47

    Performance

    Renders faster than
    65% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 68

    SEO

    Google-friendlier than
    28% of websites

jaw-pain.net

Jaw Pain, TMJ Disorders Orofacial Pain Center in Tucson Arizona - Home

Page Load Speed

3.7 sec in total

First Response

129 ms

Resources Loaded

1.5 sec

Page Rendered

2.1 sec

jaw-pain.net screenshot

About Website

Click here to check amazing Jaw Pain content. Otherwise, check out these important facts you probably never knew about jaw-pain.net

We are medical professionals who provide high-quality and patient-centered services. Your health is our priority.

Visit jaw-pain.net

Key Findings

We analyzed Jaw-pain.net page load time and found that the first response time was 129 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

jaw-pain.net performance score

47

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.8 s

11/100

10%

LCP (Largest Contentful Paint)

Value9.6 s

0/100

25%

SI (Speed Index)

Value7.3 s

29/100

10%

TBT (Total Blocking Time)

Value230 ms

86/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value10.2 s

25/100

10%

Network Requests Diagram

jaw-pain.net

129 ms

jaw-pain.net

223 ms

react.production.min.js

37 ms

react-dom.production.min.js

56 ms

fat_core.EN.js

64 ms

Our browser made a total of 46 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Jaw-pain.net, 50% (23 requests) were made to Img-fl.nccdn.net and 9% (4 requests) were made to Count.carrierzone.com. The less responsive or slowest element that took the longest time to load (786 ms) relates to the external source 0201.nccdn.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 237.4 kB (6%)

Content Size

3.7 MB

After Optimization

3.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Jaw-pain.net main page is 3.7 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. 35% of websites need less resources to load. Images take 3.2 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 143.0 kB

  • Original 169.4 kB
  • After minification 168.6 kB
  • After compression 26.5 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 143.0 kB or 84% of the original size.

Image Optimization

-1%

Potential reduce by 32.0 kB

  • Original 3.2 MB
  • After minification 3.2 MB

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. Jaw Pain images are well optimized though.

JavaScript Optimization

-23%

Potential reduce by 62.4 kB

  • Original 268.7 kB
  • After minification 244.2 kB
  • After compression 206.3 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 62.4 kB or 23% of the original size.

CSS Optimization

-1%

Potential reduce by 132 B

  • Original 17.4 kB
  • After minification 17.4 kB
  • After compression 17.2 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. Jaw-pain.net has all CSS files already compressed.

Requests Breakdown

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

Requests Now

44

After Optimization

12

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

jaw-pain.net

jaw-pain.net

129 ms

jaw-pain.net

jaw-pain.net

223 ms

react.production.min.js

react.production.min.js

37 ms

react-dom.production.min.js

react-dom.production.min.js

56 ms

fat_core.EN.js

fat_core.EN.js

64 ms

env.js

env.js

223 ms

fat_eua.EN.js

fat_eua.EN.js

98 ms

fat_freemona.css

fat_freemona.css

90 ms

fat_display.js

fat_display.js

97 ms

header.transpiled.js

header.transpiled.js

105 ms

fat_freemona.js

fat_freemona.js

102 ms

fat_display.EN.js

fat_display.EN.js

115 ms

display.m.EN.js

display.m.EN.js

118 ms

fat_display.js

fat_display.js

119 ms

fat_display.EN.js

fat_display.EN.js

139 ms

fat_display.js

fat_display.js

152 ms

fat_styles.css

fat_styles.css

137 ms

link.transpiled.js

link.transpiled.js

137 ms

display.m.EN.js

display.m.EN.js

139 ms

Gallery_display.css

Gallery_display.css

154 ms

fat_display.EN.js

fat_display.EN.js

161 ms

display.m.EN.js

display.m.EN.js

158 ms

GoogleMaps_display.css

GoogleMaps_display.css

152 ms

display.m.EN.js

display.m.EN.js

173 ms

ContactInfo_display.css

ContactInfo_display.css

168 ms

count.js

count.js

262 ms

tmj.jpg

tmj.jpg

79 ms

pi-3840x2560.jpg

pi-3840x2560.jpg

95 ms

us-nmym7fxpoke.jpeg

us-nmym7fxpoke.jpeg

613 ms

us-kevkes1_rdu.jpeg

us-kevkes1_rdu.jpeg

786 ms

us-gtod_k0dsqm.jpeg

us-gtod_k0dsqm.jpeg

478 ms

pageimage-3840x2160.jpg

pageimage-3840x2160.jpg

96 ms

background-3840x2560.jpg

background-3840x2560.jpg

166 ms

blank.gif

blank.gif

50 ms

space.gif

space.gif

40 ms

bg-sk-img.jpg

bg-sk-img.jpg

87 ms

icon_53.png

icon_53.png

64 ms

icon_02.png

icon_02.png

83 ms

ctin.php

ctin.php

78 ms

ctin.php

ctin.php

106 ms

embed

embed

300 ms

js

js

69 ms

search.js

search.js

4 ms

geometry.js

geometry.js

8 ms

main.js

main.js

18 ms

count.js

count.js

80 ms

Accessibility Review

jaw-pain.net accessibility score

80

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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.

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

jaw-pain.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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

jaw-pain.net SEO score

68

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

High

Image elements do not have [alt] attributes

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jaw-pain.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 Jaw-pain.net main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

jaw-pain.net

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