2.1 sec in total
18 ms
1.4 sec
630 ms
Visit raleigh2.com now to see the best up-to-date Raleigh 2 content and also check out these interesting facts you probably never knew about raleigh2.com
Local dining, entertainment, arts and culture, business, events, music, wine, fashion, history, and much more throughout the Triangle
Visit raleigh2.comWe analyzed Raleigh2.com page load time and found that the first response time was 18 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
raleigh2.com performance score
name
value
score
weighting
Value4.4 s
16/100
10%
Value22.7 s
0/100
25%
Value9.0 s
15/100
10%
Value840 ms
34/100
30%
Value0.025
100/100
15%
Value18.4 s
3/100
10%
18 ms
38 ms
583 ms
144 ms
184 ms
Our browser made a total of 49 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Raleigh2.com, 20% (10 requests) were made to Static.xx.fbcdn.net and 20% (10 requests) were made to Cdn1.locable.com. The less responsive or slowest element that took the longest time to load (583 ms) relates to the external source Triangledowntowner.com.
Page size can be reduced by 38.5 kB (0%)
8.7 MB
8.7 MB
In fact, the total size of Raleigh2.com main page is 8.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. 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 8.1 MB which makes up the majority of the site volume.
Potential reduce by 38.4 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 38.4 kB or 78% of the original size.
Potential reduce by 0 B
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. Raleigh 2 images are well optimized though.
Potential reduce by 60 B
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 13 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. Raleigh2.com has all CSS files already compressed.
Number of requests can be reduced by 16 (37%)
43
27
The browser has sent 43 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Raleigh 2. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
raleigh2.com
18 ms
www.triangledowntowner.com
38 ms
www.triangledowntowner.com
583 ms
application-62f8b7e3041b5cf8e2ccd1ed4ff8310bd71005f5f4cc4a161c1ed9ed43c8d23f.css
144 ms
script.js
184 ms
print-fe1b40859b2ebf3b0a55c395ad974b40f3dc0afb58a59f937c6ab67b342c3f65.css
169 ms
triangle-downtowner-logo.jpg
168 ms
frederiksted.jpg
210 ms
EMMA_2006_20-_20Jamie_20Ann_20Romero_20and_20Eric_20Bryant_20inEmma__20by_20Kate_20Hamill__20based_20on_20the_20novel_20by_20Jane_20Austen__20directed_20by_20Meredith_20McDonough_20at_20PlayMakers_20Repertory_20Company_20-_20Photo_20by_20HuthPhoto.jpg
398 ms
Triangle-Downtowner-Magazine-Issue178-1.jpg
215 ms
staff.jpg
216 ms
AIA_20tower_20plaque.jpg
202 ms
thumbnail_20for_20article.png
207 ms
best_20of_20downtowner_20article_20main_20image.jpg
186 ms
whittenburg_20tournament_20group_20photo.png
203 ms
page.php
393 ms
application-5e43a6cfb6b6f83c4d854535e8b6e6e9d001f7b875bea544bc3e971a1fa508f0.js
188 ms
init-2.min.js
380 ms
jquery-migrate-3.0.1.js
141 ms
Screen_20Shot_202017-07-10_20at_2010.22.50_20AM.png
375 ms
downtowner-magazine-issue-137.jpg
384 ms
IMG_4910.jpg
189 ms
downtowner-magazine-issue-154.jpg
180 ms
Slide10.JPG
371 ms
PJWerth_s.png
371 ms
mussels.JPG
373 ms
AIA_20tower_20plaque.jpg
170 ms
9780385543026.jpg
178 ms
Fire_20Scene.jpg
187 ms
css
88 ms
widgets.js
186 ms
otoKjNgXJiB.css
111 ms
HA2ACdUlt1V.js
176 ms
E_P-TzY6wm3.js
174 ms
guwKwycnxkZ.js
207 ms
J8JpUDMoOct.js
205 ms
p55HfXW__mM.js
205 ms
ALTQi95mOyD.js
211 ms
XQjjmb9uM86.js
212 ms
fa-regular-400-6799c999e422710f40f70a60a6138fc38106226c44d7bd1b1023f5bb65befef9.woff
103 ms
fa-solid-900-aab971ade1633ab836222074ceae0aad8a082d900908f27491b221d6e83998ca.woff
46 ms
fa-brands-400-a0375c054a0041bd58e2a0bf7fa3df7c3904bfc4f790fd24e32ff3ee70fd0eef.woff
103 ms
widget_iframe.2f70fb173b9000da126c79afe2098f02.html
135 ms
302342765_766071664792534_5427495796684546842_n.jpg
150 ms
451230840_1245155770217452_7802835825355080656_n.jpg
175 ms
gl6i0u_T8Oq.js
53 ms
UXtr_j2Fwe-.png
37 ms
settings
115 ms
timeline.e108540dddc96e4b707f5cf259a582d7.js
4 ms
raleigh2.com accessibility score
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
ARIA IDs are not unique
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
raleigh2.com 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
raleigh2.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Raleigh2.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 Raleigh2.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.
raleigh2.com
Open Graph data is detected on the main page of Raleigh 2. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: