4.7 sec in total
64 ms
801 ms
3.8 sec
Welcome to sfexaminer.com homepage info - get ready to check Sf Examiner best content for United States right away, or after learning these important things about sfexaminer.com
The San Francisco Examiner is the city's source for breaking news, local coverage and investigative journalism.
Visit sfexaminer.comWe analyzed Sfexaminer.com page load time and found that the first response time was 64 ms and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
sfexaminer.com performance score
name
value
score
weighting
Value2.9 s
53/100
10%
Value18.4 s
0/100
25%
Value15.3 s
1/100
10%
Value4,780 ms
0/100
30%
Value0.094
91/100
15%
Value34.2 s
0/100
10%
64 ms
116 ms
7 ms
37 ms
78 ms
Our browser made a total of 64 requests to load all elements on the main page. We found that 5% of them (3 requests) were addressed to the original Sfexaminer.com, 42% (27 requests) were made to S79f01z693v3ecoes3yyjsg1.wpengine.netdna-cdn.com and 34% (22 requests) were made to Engine.adzerk.net. The less responsive or slowest element that took the longest time to load (283 ms) relates to the external source Engine.adzerk.net.
Page size can be reduced by 1.1 MB (4%)
28.1 MB
27.0 MB
In fact, the total size of Sfexaminer.com main page is 28.1 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. Only a small number of websites need less resources to load. Images take 26.9 MB which makes up the majority of the site volume.
Potential reduce by 116.9 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 116.9 kB or 86% of the original size.
Potential reduce by 198.3 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. Sf Examiner images are well optimized though.
Potential reduce by 738.7 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 738.7 kB or 70% of the original size.
Potential reduce by 13.3 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. Sfexaminer.com needs all CSS files to be minified and compressed as it can save up to 13.3 kB or 76% of the original size.
Number of requests can be reduced by 31 (52%)
60
29
The browser has sent 60 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Sf Examiner. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 32 to 1 for JavaScripts and as a result speed up the page load time.
sfexaminer.com
64 ms
www.sfexaminer.com
116 ms
autoptimize_2afae183797ec1bc19b278e64b3adb36.css
7 ms
css
37 ms
jquery.min.js
78 ms
jquery-1.9.1.js
7 ms
autoptimize_10e98899c7c0a7b9126539f575af7f3b.js
5 ms
embed.js
79 ms
ados.js
171 ms
analytics.js
171 ms
wp-emoji-release.min.js
233 ms
close-white.svg
151 ms
navburger.svg
143 ms
afterdark.png
146 ms
examiner-logo-REV.png
147 ms
facebook.svg
148 ms
twitter.svg
151 ms
examiner-logo.jpg
154 ms
IMG_2427.jpg
239 ms
sf.crooks.0228.jpg
219 ms
sf.fortfunston.0228.jpg
220 ms
sf.idrivesf.0226.jpg
228 ms
sf.brokeass.0225.jpg
226 ms
TentCityMove-8.jpg
258 ms
LowellWalkoutWeb.jpg
223 ms
Chinese-Parade-13-of-15-e1456092515528.jpg
222 ms
sf.cleanpower.0229.jpg
229 ms
curry.0229.jpg
228 ms
AP_948158959034.jpg
231 ms
AP_264834851265.jpg
232 ms
AP_177997685858-e1456476485831.jpg
229 ms
JayPic.0222.jpg
238 ms
22e77119e116db0a910f6a706700bdd5.jpg
231 ms
TentCityMove-8-1.jpg
246 ms
AOSCARWINNERS-e1456730588111.jpg
232 ms
AOHHELLO-e1456535911342.jpg
233 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
218 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
228 ms
callback=_nw2e.closures.c0
95 ms
getids
97 ms
ados
94 ms
ados
90 ms
ados
86 ms
ados
96 ms
ados
87 ms
ados
86 ms
ados
88 ms
ados
89 ms
ados
87 ms
ados
89 ms
ados
90 ms
ados
96 ms
ados
96 ms
ados
91 ms
ados
91 ms
ados
92 ms
ados
282 ms
ados
283 ms
ados
279 ms
ados
277 ms
ados
276 ms
ados
278 ms
collect
259 ms
Widget.js
189 ms
sfexaminer.com accessibility score
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
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
The document uses <meta http-equiv="refresh">
sfexaminer.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
sfexaminer.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 Sfexaminer.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 Sfexaminer.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.
sfexaminer.com
Open Graph description is not detected on the main page of Sf Examiner. 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: