3.4 sec in total
260 ms
2.8 sec
357 ms
Visit edgerestaurant.net now to see the best up-to-date Edge Restaurant content and also check out these interesting facts you probably never knew about edgerestaurant.net
Edge Restaurant & Lounge is located in Bethlehem, PA. Proudly serving the Lehigh Valley and beyond. Visit today!
Visit edgerestaurant.netWe analyzed Edgerestaurant.net page load time and found that the first response time was 260 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
edgerestaurant.net performance score
name
value
score
weighting
Value3.4 s
36/100
10%
Value3.4 s
66/100
25%
Value7.0 s
33/100
10%
Value220 ms
88/100
30%
Value0.365
29/100
15%
Value8.3 s
40/100
10%
260 ms
507 ms
44 ms
43 ms
66 ms
Our browser made a total of 75 requests to load all elements on the main page. We found that 23% of them (17 requests) were addressed to the original Edgerestaurant.net, 53% (40 requests) were made to Fonts.gstatic.com and 7% (5 requests) were made to C0.wp.com. The less responsive or slowest element that took the longest time to load (570 ms) relates to the external source App.getreviewsup.com.
Page size can be reduced by 166.9 kB (22%)
759.5 kB
592.6 kB
In fact, the total size of Edgerestaurant.net main page is 759.5 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 332.1 kB which makes up the majority of the site volume.
Potential reduce by 154.3 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 154.3 kB or 83% of the original size.
Potential reduce by 1.0 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. Edge Restaurant images are well optimized though.
Potential reduce by 11.2 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.
Potential reduce by 445 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. Edgerestaurant.net has all CSS files already compressed.
Number of requests can be reduced by 21 (66%)
32
11
The browser has sent 32 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Edge Restaurant. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
edgerestaurant.net
260 ms
www.edgerestaurant.net
507 ms
mediaelementplayer-legacy.min.css
44 ms
wp-mediaelement.min.css
43 ms
wpo-minify-header-ad125350.min.css
66 ms
image-cdn.js
151 ms
index.js
188 ms
index.js
188 ms
jquery.min.js
47 ms
jquery-migrate.min.js
47 ms
scripts.min.js
333 ms
smoothscroll.js
186 ms
moment.js
252 ms
jquery.datetimepicker.full.min.js
374 ms
dtpicker.js
265 ms
common.js
263 ms
e-202403.js
46 ms
js
570 ms
floating.js
270 ms
gtm.js
78 ms
fbevents.js
45 ms
restaurant-lounge-bar-304563-min.jpg
328 ms
restaurant-lounge-bar-304612.png
67 ms
et-divi-dynamic-14-late.css
179 ms
Asset-23.png
245 ms
restaurant-lounge-bar-304748-sm-min.png
65 ms
surv-teaseAsset-29md.png
64 ms
analytics.js
87 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVQ.woff
123 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf
123 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVQ.woff
124 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVc.ttf
128 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVQ.woff
125 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf
127 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVQ.woff
124 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf
125 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVQ.woff
126 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf
127 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKeiunDZbtU.woff
128 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKeiunDZbtY.ttf
134 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKfFunDZbtU.woff
131 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKfFunDZbtY.ttf
134 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKfsunDZbtU.woff
133 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKfsunDZbtY.ttf
135 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKebunDZbtU.woff
135 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKebunDZbtY.ttf
138 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKd3vXDZbtU.woff
138 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKd3vXDZbtY.ttf
137 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKdFvXDZbtU.woff
137 ms
nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKdFvXDZbtY.ttf
139 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw3aXw.woff
138 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw3aX8.ttf
141 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw3aXw.woff
139 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw3aX8.ttf
140 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw3aXw.woff
140 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw3aX8.ttf
141 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw3aXw.woff
141 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw3aX8.ttf
143 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw3aXw.woff
144 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw3aX8.ttf
144 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w3aXw.woff
144 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w3aX8.ttf
144 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w3aXw.woff
141 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w3aX8.ttf
144 ms
modules.woff
117 ms
style.min.css
21 ms
collect
72 ms
collect
83 ms
collect
197 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w3aXw.woff
31 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w3aX8.ttf
33 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w3aXw.woff
32 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w3aX8.ttf
31 ms
js
104 ms
ga-audiences
47 ms
edgerestaurant.net accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
edgerestaurant.net best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
edgerestaurant.net SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Edgerestaurant.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 Edgerestaurant.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.
edgerestaurant.net
Open Graph data is detected on the main page of Edge Restaurant. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: